Re: fixing LISTEN/NOTIFY
От | Jim C. Nasby |
---|---|
Тема | Re: fixing LISTEN/NOTIFY |
Дата | |
Msg-id | 20051008204043.GS36108@pervasive.com обсуждение исходный текст |
Ответ на | Re: fixing LISTEN/NOTIFY (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: fixing LISTEN/NOTIFY
|
Список | 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 по дате отправления: