From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Reduce scope of changes for COPY FREEZE. |
Date: | 2012-12-02 20:57:17 |
Message-ID: | E1TfGbF-0004yy-Nt@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Reduce scope of changes for COPY FREEZE.
Allow support only for freezing tuples by explicit
command. Previous coding mistakenly extended
slightly beyond what was agreed as correct on -hackers.
So essentially a partial revoke of earlier work,
leaving just the COPY FREEZE command.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/5457a130d3a66db807d1e0ee2b8e829321809b83
Modified Files
--------------
src/backend/access/heap/heapam.c | 13 +++-----
src/backend/commands/copy.c | 9 ++---
src/include/access/heapam.h | 3 +-
src/test/regress/expected/copy2.out | 60 +++++++++++++++++++++-------------
src/test/regress/sql/copy2.sql | 19 ++++++-----
5 files changed, 57 insertions(+), 47 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-12-02 21:18:29 | pgsql: Recommend triggers, not rules, in the CREATE VIEW reference page |
Previous Message | Tom Lane | 2012-12-02 20:21:11 | pgsql: Don't advance checkPoint.nextXid near the end of a checkpoint se |