On Wed, Nov 7, 2012 at 10:34 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> For 9.2 we discussed having COPY setting tuples as frozen. Various
> details apply.
> Earlier threads:
> "RFC: Making TRUNCATE more "MVCC-safe"
> "COPY with hints, rebirth"
>
> I was unhappy with changing the behaviour of TRUNCATE, and still am.
> So the proposal here is to have a specific modifier on TRUNCATE
> command that makes it MVCC safe by throwing a serialization error.
I don't think I understand the proposal. Under what circumstances
would it throw a serialization error?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
