Re: Thoughts about bug #3883 - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Thoughts about bug #3883
Date
Msg-id 87abmt631v.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Thoughts about bug #3883  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Thoughts about bug #3883  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> The simplest fix seems to be to invent an additional flag variable
> "signalAwaited" which is set/cleared by ProcWaitForSignal and checked by
> LockWaitCancel. This would make cancelling out of a ProcWaitForSignal call
> exactly analogous to cancelling out of a heavyweight-lock acquisition.

Is that the flag that is an assertion that no cleanup is needed? Or is that
something else?

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support!


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proposal: Integrity check
Next
From: Gregory Stark
Date:
Subject: Re: Proposal: Integrity check