[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> Tom Lane writes:
> > 1. Since the trigger is executed as soon as a tuple is inserted/
> > updated/deleted, it will write pg_pwd before the transaction is
> > committed. If you then abort the transaction, pg_pwd contains wrong
> > data.
> Wow, that implies that every trigger that contains non-database
> side-effects is potentially bogus. That never occured to me. Perhaps (as a
> future plan), it would be a good idea to have deferred triggers as well?
> Now that I think of it, wasn't that the very reason Jan had to invent the
> separate constraint triggers?
Yes! I remember him talking about this. I bet you can just modify your
trigger to be of that type.
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
In response to
pgsql-hackers by date
|Next:||From: Hiroshi Inoue||Date: 2000-02-28 02:00:35|
|Subject: RE: [HACKERS] Re: ALTER TABLE DROP COLUMN|
|Previous:||From: Bruce Momjian||Date: 2000-02-28 00:17:08|
|Subject: Re: [HACKERS] Re: ALTER TABLE DROP COLUMN|