From: | Jeff Davis <list-pgsql-hackers(at)empires(dot)org> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | listen/notify argument (old topic revisited) |
Date: | 2002-07-02 09:37:19 |
Message-ID: | 200207020237.19838.list-pgsql-hackers@empires.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
A while ago, I started a small discussion about passing arguments to a NOTIFY
so that the listening backend could get more information about the event.
There wasn't exactly a consensus from what I understand, but the last thing I
remember is that someone intended to speed up the notification process by
storing the events in shared memory segments (IIRC this was Tom's idea). That
would create a remote possibility of a spurious notification, but the idea is
that the listening application can check the status and determine what
happened.
I looked at the TODO, but I couldn't find anything, nor could I find anything
in the docs.
Is someone still interested in implementing this feature? Are there still
people who disagree with the above implementation strategy?
Regards,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-07-02 13:27:02 | Re: regress/results directory problem |
Previous Message | Hannu Krosing | 2002-07-02 08:40:46 | Re: aggregate that returns array |