From: | tgl(at)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql-server/src/backend commands/async.c tcop ... |
Date: | 2002-09-16 01:24:41 |
Message-ID: | 20020916012441.7A714475425@postgresql.org |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: tgl(at)postgresql(dot)org 02/09/15 21:24:41
Modified files:
src/backend/commands: async.c
src/backend/tcop: postgres.c
Log message:
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian - CVS | 2002-09-16 02:47:05 | pgsql-server/doc/TODO.detail win32 |
Previous Message | Peter Eisentraut - PostgreSQL | 2002-09-15 13:04:16 | pgsql-server/ oc/src/sgml/ref/create_cast.sgml ... |