From: | Chris Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: About dropped notifications |
Date: | 2005-08-29 22:05:54 |
Message-ID: | 60u0h8760t.fsf@dba2.int.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) writes:
> CSN <cool_screen_name90001(at)yahoo(dot)com> writes:
>> I'm considering setting up a script that listens for
>> notifications for a table and if a row is deleted the
>> script will delete that row's corresponding files. If
>> there are thousands of rows in the table, and I do
>> "delete from table", or even "delete from table where
>> id >1000 and id<2000", will the script be notified of
>> the deletion of each and every row (and subsequently
>> be able to delete that row's files), or will only one
>> notify event be received (or some number less than the
>> actual number of rows deleted)?
>
> Depends where you are doing the notify from ... but I think
> with the current implementation, a transaction will emit only
> one notify per notify event name, even if NOTIFY is executed
> many times within the transaction.
An interesting question is whether or not the relevant tuple in
pg_listener gets invalidated once, or whether doing 2500 attempted
NOTIFY requests blows through 2500 copies.
--
"cbbrowne","@","cbbrowne.com"
http://www.ntlug.org/~cbbrowne/internet.html
"As long as each individual is facing the TV tube alone, formal
freedom poses no threat to privilege." --Noam Chomsky
From | Date | Subject | |
---|---|---|---|
Next Message | John Surnow | 2005-08-29 23:16:46 | "GiST access is not concurrent" |
Previous Message | Moises Alberto Lindo Gutarra | 2005-08-29 21:56:31 | Re: Select gives the wrong results |