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

From Joachim Wieland
Subject Re: Listen / Notify - what to do when the queue is full
Date
Msg-id dc7b844e1001080448t55bff743q7bc7852c3761b83f@mail.gmail.com
Whole thread Raw
In response to Re: Listen / Notify - what to do when the queue is full  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Listen / Notify - what to do when the queue is full
Re: Listen / Notify - what to do when the queue is full
List pgsql-hackers
On Thu, Jan 7, 2010 at 7:40 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> Joachim - This no longer applies - please rebase, repost, and add a
> link to the new version to the commitfest app.

Updated patch attached.

>From my point of view these are the current open questions:

- is the general approach reasonable (i.e. to put notifications into
an slru-based queue instead of into shared memory to allow for a
better handling of notification bursts)

- is the transactional behavior correct (see upthread)

- do we need to limit the payload to pure ASCII ? I think yes, we need
to. I also think we need to reject other payloads with elog(ERROR...).

- how to deal with 2PC (see upthread) ?

- how to deal with hot standby (has not been discussed yet)


Joachim

Attachment

pgsql-hackers by date:

Previous
From: Tim Bunce
Date:
Subject: Initial refactoring of plperl.c - updated
Next
From: Andrew Dunstan
Date:
Subject: Re: RFC: PostgreSQL Add-On Network