On Thu, Jan 5, 2017 at 4:48 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Robert Haas <robertmh...@gmail.com> 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.
Oh ho. So the worst consequence of this is a backend-lifetime leak,
not a cluster-lifetime leak. That's good, at least.
The Enterprise PostgreSQL Company
Sent via pgsql-hackers mailing list (firstname.lastname@example.org)
To make changes to your subscription: