On 9 November 2012 15:46, Simon Riggs <si...@2ndquadrant.com> wrote: > Altering TRUNCATE so it behaves perfectly from an MVCC/Serializable > perspective is a much bigger, and completely different goal, as well > as something I don't see as desirable anyway for at least 2 good > reasons, as explained. IMHO if people want MVCC/Serializable > semantics, use DELETE, possibly spending time to make unqualified > DELETE do some fancy TRUNCATE-like tricks with relfilenodes.
We spent a lot of time in 9.2 making TRUNCATE/reload of a table "just work", rather than implementing a REPLACE command. ISTM strange to throw away all that effort, changing behaviour of TRUNCATE and thus forcing the need for a REPLACE command after all. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
