Re: COPY with hints, rebirth

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "Noah Misch" <noah(at)leadboat(dot)com>
Cc: "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY with hints, rebirth
Date: 2012-03-02 21:12:10
Message-ID: 4F50E34A0200002500045E65@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Noah Misch <noah(at)leadboat(dot)com> wrote:

> Incidentally, I contend that we should write frozen tuples to
> new/truncated tables unconditionally.

+1

> The current behavior of making old snapshots see the table as
> empty violates atomicity at least as badly as letting those
> snapshots see the future-snapshot contents.

Right, there was no point where the table existed as empty at the
end of a transaction, so it is quite broken as things stand now.

> But Marti has a sound proposal that would interact with your
> efforts here to avoid violating atomicity at all

Well, getting it right is certainly better than moving from a slow
non-conforming behavior to a fast non-conforming behavior. ;-)

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-03-02 21:50:46 Re: Runtime SHAREDIR for testing CREATE EXTENSION
Previous Message Noah Misch 2012-03-02 20:58:34 Re: COPY with hints, rebirth