Commits 8de72b and 5457a1 (COPY FREEZE) - Mailing list pgsql-hackers

From Jeff Davis
Subject Commits 8de72b and 5457a1 (COPY FREEZE)
Date
Msg-id 1354584841.19553.215.camel@sussancws0025
Whole thread Raw
Responses Re: Commits 8de72b and 5457a1 (COPY FREEZE)  (Simon Riggs <simon@2ndquadrant.com>)
Re: Commits 8de72b and 5457a1 (COPY FREEZE)  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8de72b66a2edcf12c812de0a73bd50b6b7d81d62

Part of that patch was reverted later:

http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=5457a130d3a66db807d1e0ee2b8e829321809b83

I assume that refers to the discussion here:

http://archives.postgresql.org/pgsql-hackers/2012-02/msg01177.php

But that was quite a while ago, so is there a more recent discussion
that prompted this commit now?

I am a little confused about the case where setting HEAP_XMIN_COMMITTED
when loading the table in the same transaction is wrong. There was some
discussion about subtransactions, but those problems only seemed to
appear when the CREATE and the INSERT/COPY happened in different
subtransactions.

So, I guess my question is, why the partial revert?

Regards,Jeff Davis






pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: json accessors
Next
From: Josh Berkus
Date:
Subject: Re: ALTER TABLE ... NOREWRITE option