Re: fixing LISTEN/NOTIFY - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: fixing LISTEN/NOTIFY
Date
Msg-id 20051008204043.GS36108@pervasive.com
Whole thread Raw
In response to Re: fixing LISTEN/NOTIFY  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: fixing LISTEN/NOTIFY
List pgsql-hackers
On Thu, Oct 06, 2005 at 10:30:24AM -0400, Tom Lane wrote:
> Heikki Linnakangas <hlinnaka@iki.fi> writes:
> > It might make sense to change the semantics so that we never lose a 
> > notification, if we're going to implement NOTIFY 'msg', but that's another 
> > discussion.
> 
> That's pretty much a given --- the ability to pass some payload data in
> notifications has been on the TODO list for a very long time.  I don't
> think we're going to reimplement listen/notify without adding it.

Maybe I'm missing something, but is it possible to ensure notifications
aren't lost using Heikki's method, since everything's only in shared
memory? Or is the idea that stuff would not survive a backend crash?
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: avoid pulling up subquerys that contain volatile functions?
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Vote needed: revert beta2 changes or not?