Tom Lane 53e95eee84 Fix for rare race-condition-like failure: if a backend receives SIGUSR2
(notify/SI-overrun interrupt) while it is in process of doing proc_exit,
it is possible for Async_NotifyHandler() to try to start a transaction
when one is already running.  This leads to Asserts() or worse.  I think
it may only be possible to occur when frontend synchronization is lost
(ie, the elog(FATAL) in SocketBackend() fires), but that is a standard
occurrence after error during COPY.  In any case, I have seen this
failure occur during regression tests, so it is definitely possible.
2002-09-16 01:24:41 +00:00
..
2002-09-14 13:46:24 +00:00
2002-09-05 18:28:46 +00:00
2002-09-04 20:31:48 +00:00
2002-09-05 18:28:46 +00:00
2002-09-04 19:11:06 +00:00
2002-09-05 18:28:46 +00:00
2002-09-05 18:28:46 +00:00
2002-09-05 18:28:46 +00:00