"Stephen Denne" <[EMAIL PROTECTED]> writes:
> Aside: It is currently more cumbersome to get a function to run, if needed,
> at commit. Ideal solution would be something like "EXECUTE ON COMMIT
> my_function()" or maybe "SAVEPOINT my_name ON COMMIT my_function()", but
> these suggestions are made without investigating what provision the SQL
> standard has made to address this need.
There is none, and the reason seems pretty obvious to me. What if your
"on commit" function fails? Or if you have two, and the second one
fails? Or even more to the point, the second one does something that
the first one expected to see the effects of?
Transaction commit is an exceedingly subtle and carefully structured
thing. Throwing random user-defined code into it ain't gonna happen.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
