From: | Neil Conway <neilc(at)samurai(dot)com> |
---|---|
To: | <enio(at)pmpf(dot)rs(dot)gov(dot)br> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Catching "UPDATE 0" |
Date: | 2003-11-10 18:56:49 |
Message-ID: | 87r80gyrv2.fsf@mailbox.samurai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
<enio(at)pmpf(dot)rs(dot)gov(dot)br> writes:
> I am trying to catch the "UPDATE 0" condition in postgresql.
> I have tried it using triggers, but they are only fired when there
> effectively is an update.
You could try using an AFTER STATEMENT trigger (which will be invoked
even if zero rows are updated), and checking the size of the set of
modified rows ... except that we currently don't provide a way for
per-statement triggers to access the set of modified tuples.
If someone implements that functionality (which is on the TODO list),
that would be a clean solution to your problem.
-Neil
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-11-10 18:57:01 | Re: Experimental patch for inter-page delay in VACUUM |
Previous Message | Bruce Momjian | 2003-11-10 18:52:34 | Re: Experimental patch for inter-page delay in VACUUM |