| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: Truncate Triggers |
| Date: | 2008-01-26 16:57:09 |
| Message-ID: | 20080126165709.GB828@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jan 26, 2008 at 04:33:53PM +0000, Gregory Stark wrote:
> "Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net> writes:
>
> > the idea of implementing row level visibility in statement level triggers
>
> Huh?
I think he means that statement level triggers can see the rows that
got affected, presumably by NEW representing a tuplestore. How that
would work for BEFORE STATEMENT triggers I don't know.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Those who make peaceful revolution impossible will make violent revolution inevitable.
> -- John F Kennedy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2008-01-26 17:07:25 | Re: plperl: Documentation on BYTEA decoding is wrong |
| Previous Message | Andreas Pflug | 2008-01-26 16:55:47 | Re: Truncate Triggers |