pgsql: Clarify that COPY FREEZE is not a hard rule.

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Clarify that COPY FREEZE is not a hard rule.
Date: 2012-12-07 13:00:36
Message-ID: E1TgxXg-0003n6-Cr@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Clarify that COPY FREEZE is not a hard rule.
Remove message when FREEZE not honoured,
clarify reasons in comments and docs.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/1eb6cee499d19fc9204e059ba37fc2dac32e2f25

Modified Files
--------------
doc/src/sgml/ref/copy.sgml | 8 +++++---
src/backend/commands/copy.c | 10 +++++-----
2 files changed, 10 insertions(+), 8 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2012-12-07 13:28:58 pgsql: Optimize COPY FREEZE with CREATE TABLE also.
Previous Message Tom Lane 2012-12-07 04:10:08 pgsql: Improve pl/pgsql to support composite-type expressions in RETURN