Stephan Szabo <[EMAIL PROTECTED]> writes:
> Yeah, I think there are a few possibilities around truncate inside a
> savepoint that's rolledback that we have to be careful of.
Yuck :-(
> If we could mark the entries in some way so we knew whether or not they
> were made obsolete by a truncate of our own tranasaction or a committed or
> rolled back past subtransaction of ours, we could probably make both of
> these work nicely.
That seems much more trouble than it's worth, unless someone can
convince me that this isn't a corner case with little real-world value.
Furthermore, this still doesn't address the worry about whether there
are cases where dropping the trigger calls would be inappropriate.
I propose just having TRUNCATE check for pending triggers on the
target tables, and throw an error if there are any.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
