Re: [HACKERS] update_pg_pwd trigger does not work very well
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] update_pg_pwd trigger does not work very well |
Дата | |
Msg-id | 200002280018.TAA11340@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] update_pg_pwd trigger does not work very well (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: [HACKERS] update_pg_pwd trigger does not work very well
|
Список | pgsql-hackers |
[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@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
В списке pgsql-hackers по дате отправления: