with your reminder I had a look at the code of the LISTEN/NOTIFY implementation, NOTIFY <name> 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 <yhavinga@xxxxxxxxx>: > 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 hundreds >> seconds, which is too long to be acceptable. >> > > Hello Gavin, > > The following might help from the notify docs: > > "NOTIFY behaves like Unix signals in one important respect: if the same > notification name is signaled multiple times in quick succession, recipients > might get only one notification event for several executions of NOTIFY." > > So if your notify for instance could also add a unique number to the > notification name, then it will probably work as expected. > > Regards, > Yeb Havinga > > > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
