Re: notification payloads

Ühel kenal päeval, T, 2007-03-27 kell 07:11, kirjutas Andrew Dunstan:
>
> Hannu Krosing wrote:
> > So perhaps it Alvaros proposal can be rephrased thus:
> > "Why have the name on each message? The names are already stored in
> > listen table, just reuse numeric identifier pointing to item in that
> > table. That gives you room for a lot more messages."
> >
> > If there is no name in listen table, it means that nobody is interested
> > and the message can be dropped right away.
> >
> >
>
> Er, what listen table?

equivalent of pg_listener, see my mail with attached .sql

> The only thing that will be in shared memory is a
> queue and some bookkeeping (queue head per backend). Each backend will
> be responsible for catching the notifications it is interested in and
> discarding the rest

At least the list of which backends listen to which events should be
also in shared mem.

How else would we know how many copies to make for each backend or when
we can release the memory in case we make one copy ?

> (see earlier discussion).

could you post a link to archives ?

I could not find anything relevant in the discussion link from the head
of this mail thread.

> cheers
>
> andrew
--
----------------
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia

Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com

NOTICE: This communication contains privileged or other confidential
information. If you have received it in error, please advise the sender
by reply email and immediately delete the message and any attachments
without copying or disclosing the contents.