Robert Haas <[email protected]> writes:
> I think we have run into this kind of issue before. I wonder if
> there's any way to insert some kind of a guard - e.g. detect at
> backend startup time that the semaphore has a non-zero value and fix
> it, issuing a warning along the way... maybe something like:
See the PGSemaphoreReset near the end of InitProcess.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
