Re: LISTEN/NOTIFY and notification timing guarantees - Mailing list pgsql-hackers

From Tom Lane
Subject Re: LISTEN/NOTIFY and notification timing guarantees
Date
Msg-id 14936.1266354911@sss.pgh.pa.us
Whole thread Raw
In response to Re: LISTEN/NOTIFY and notification timing guarantees  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
Merlin Moncure <mmoncure@gmail.com> writes:
> On Tue, Feb 16, 2010 at 10:38 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 2. Add an extra lock to serialize writers to the queue, so that messages
>> are guaranteed to be added to the queue in commit order. �As long as

> fwiw, I think you're definitely on the right track.  IMO, any scenario
> where an issued notification ends up being deferred for an indefinite
> period of time without alerting the issuer should be avoided if at all
> possible.  Just to clarify though, does your proposal block all
> notifiers if any uncommitted transaction issued a notify?

It will block other notifiers until the transaction releases its locks,
which should happen pretty promptly --- there are no user-accessible
reasons for it to wait.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: LISTEN/NOTIFY and notification timing guarantees
Next
From: Bruce Momjian
Date:
Subject: Re: Re: [GENERAL] FM format modifier does not remove leading zero from year