-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
>>> CREATE OR REPLACE RULE send_notify AS ON INSERT TO log DO
>>> ALSO NOTIFY logevent;
>
Hi, Greg,
Thanks for your reply, and I described my case more clearly inline.
Regards, Gavin Mu
2010/2/1 Greg Sabino Mullane :
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
>
>> I am prototyping a system which sends all INSERT/UPDATE/DELETE events
>> to a third party software, I do:
with your reminder I had a look at the code of the LISTEN/NOTIFY
implementation, NOTIFY will send SIGUSR2 signal to the backend
if it's not for itself. I guess frequent singal handling can't be
handled on time.
2010/2/1 Yeb Havinga :
> Gavin Mu wrote:
>>
>> CREATE OR REPLACE RULE send_notify AS O
Gavin Mu wrote:
CREATE OR REPLACE RULE send_notify AS ON INSERT TO log DO ALSO NOTIFY logevent;
..
when I use 3 similar programs to feed data, which means about 75
events every second, I found that Postgres didn't send NOTIFY
opportunely, since the client do SELECT query every several hundre
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> I am prototyping a system which sends all INSERT/UPDATE/DELETE events
> to a third party software, I do:
Gavin Mu wrote:
CREATE OR REPLACE RULE send_notify AS ON INSERT TO log DO ALSO NOTIFY logevent;
..
when I use 3 similar programs to feed data, which means about 75
events every second, I found that Postgres didn't send NOTIFY
opportunely, since the client do SELECT query every several hundre
Hi,
I am prototyping a system which sends all INSERT/UPDATE/DELETE events
to a third party software, I do:
CREATE TABLE data (id Serial PRIMARY KEY, data VARCHAR(255));
CREATE TABLE log (op CHAR(6), id integer, data VARCHAR(255));
CREATE OR REPLACE RULE send_notify AS ON INSERT TO log DO ALSO NOT
