On Fri, Nov 9, 2012 at 8:22 AM, Kevin Grittner <kgri...@mail.com> wrote: > Robert Haas wrote: > >> What I've been wondering since this last came up is whether we >> could use some variant of the SIREAD locks Kevin introduced for SSI >> to handle this case - essentially have the transaction doing the >> TRUNCATE make an entry in the lock table that will force a >> serialization failure for any backend which accesses the table with >> a snapshot that can't see the truncating transaction's XID. > > It seems to me that the goal would be to make this semantically > idential to the behavior users would see if an unqualified DELETE > were run against the table rather than a TRUNCATE. To wit:
but, triggers would not fire, right? merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
