The docs state:
"NOTIFY behaves like Unix signals in one important
respect: if the same notification name is signaled
multiple times in quick succession, recipients may get
only one notification event for several executions of
NOTIFY. So it is a bad idea to depend on the number of
notifications re
CSN <[EMAIL PROTECTED]> 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 tab
[EMAIL PROTECTED] (Tom Lane) writes:
> CSN <[EMAIL PROTECTED]> 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
>> "
Chris Browne <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Tom Lane) writes:
>> 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 rel
CSN <[EMAIL PROTECTED]> 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.
One way to deal with this would be to have a boolean flag in the table like
"deleted". Update that
