Re: Listen / Notify - what to do when the queue is full - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Listen / Notify - what to do when the queue is full
Date
Msg-id 16253.1258648912@sss.pgh.pa.us
Whole thread Raw
In response to Re: Listen / Notify - what to do when the queue is full  ("Florian G. Pflug" <fgp@phlo.org>)
Responses Re: Listen / Notify - what to do when the queue is full
List pgsql-hackers
"Florian G. Pflug" <fgp@phlo.org> writes:
> Tom Lane wrote:
>> This is still ignoring the complaint: you are creating a clear risk 
>> that COMMIT PREPARED will fail.

> I'd see no problem with "COMMIT PREPARED" failing, as long as it was
> possible to retry the COMMIT PREPARED at a later time. There surely are
> other failure cases for COMMIT PREPARED too, like an IO error that
> prevents the clog bit from being set, or a server crash half-way through
> COMMIT PREPARED.

Yes, there are failure cases that are outside our control.  That's no
excuse for creating one that's within our control.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: Listen / Notify - what to do when the queue is full
Next
From: "Kevin Grittner"
Date:
Subject: Re: Timezones (in 8.5?)