Re: Listen / Notify rewrite - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Listen / Notify rewrite
Date
Msg-id 24189.1258321691@sss.pgh.pa.us
Whole thread Raw
In response to Re: Listen / Notify rewrite  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Listen / Notify rewrite
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> On Wed, 2009-11-11 at 22:25 +0100, Joachim Wieland wrote:
>> 3. Every distinct notification is delivered.
>> Regarding performance, the slru-queue is not fsync-ed to disk

> These two statements seem to be in opposition. How do you know a
> notification will be delivered if the queue is non-recoverable?

You misunderstand the requirements.  LISTEN notifications are *not*
meant to survive a database crash, and never have been.  However,
so long as both client and server stay up, they must be reliable.
If the client has to poll database state because it might have
missed a notification, the feature is just a waste of time.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: named parameters in SQL functions
Next
From: Tom Lane
Date:
Subject: Re: patch - Report the schema along table name in a referential failure error message