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 3160.1258598961@sss.pgh.pa.us
Whole thread Raw
In response to Re: Listen / Notify - what to do when the queue is full  (Joachim Wieland <joe@mcknight.de>)
List pgsql-hackers
Joachim Wieland <joe@mcknight.de> writes:
> The sequence in CommitTransaction() is like that:

> 1) add notifications to queue
> 2) commit to clog
> 3) signal backends

> Only those backends are signalled that listen to at least one channel,
> if the notify system isn't in use, then nobody will ever be signalled
> anyway.

> If a backend is reading a transaction id that has not yet committed,
> it will not deliver the notification.

But you were saying that this patch would enable sending more data than
would fit in the queue.  How will that happen if the other backends
don't look at the queue until you signal them?
        regards, tom lane


pgsql-hackers by date:

Previous
From: gabrielle
Date:
Subject: Review: psql-wrap-formatting/Unicode UTF-8 table formatting for psql text output
Next
From: Tom Lane
Date:
Subject: Re: "Not safe to send CSV data" message