Re: [HACKERS] implementing NOTIFY with message parameter

2005-05-12 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > On Thu, May 12, 2005 at 10:48:50AM -0400, Tom Lane wrote: >> If you are looking for an existing tool to adapt, I think the sinval >> messaging mechanism is a FAR better prototype. > Hmm. The problem is that it's easy to do something if the sinval queue

Re: [HACKERS] implementing NOTIFY with message parameter

2005-05-12 Thread Alvaro Herrera
On Thu, May 12, 2005 at 10:48:50AM -0400, Tom Lane wrote: > Alvaro Herrera <[EMAIL PROTECTED]> writes: > > On Thu, May 12, 2005 at 10:09:23AM -0400, Tom Lane wrote: > >> Please review the archived discussions about reimplementing NOTIFY using > >> only shared memory, no tables. > > > Maybe this ca

Re: [HACKERS] implementing NOTIFY with message parameter

2005-05-12 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > On Thu, May 12, 2005 at 10:09:23AM -0400, Tom Lane wrote: >> Please review the archived discussions about reimplementing NOTIFY using >> only shared memory, no tables. > Maybe this can be done using two SLRU areas like we did for multixact. If you are

Re: [HACKERS] implementing NOTIFY with message parameter

2005-05-12 Thread Alvaro Herrera
On Thu, May 12, 2005 at 10:09:23AM -0400, Tom Lane wrote: > Andras Kadinger <[EMAIL PROTECTED]> writes: > > ... I therefore invented pg_notify: > > Please review the archived discussions about reimplementing NOTIFY using > only shared memory, no tables. Maybe this can be done using two SLRU areas

Re: [HACKERS] implementing NOTIFY with message parameter

2005-05-12 Thread Tom Lane
Andras Kadinger <[EMAIL PROTECTED]> writes: > ... I therefore invented pg_notify: Please review the archived discussions about reimplementing NOTIFY using only shared memory, no tables. The pg_listener table causes a number of performance problems, and I think that getting rid of it should be a t

[HACKERS] implementing NOTIFY with message parameter

2005-05-12 Thread Andras Kadinger
Greetings everyone, Beginner in PostgreSQL internals, seeking the insight of more experienced. " (At present, the extra field is unused and will always point to an empty string.)" - http://www.postgresql.org/docs/8.0/static/libpq-notify.html regarding PGnotify returned by PQnotifies I would lik