From 1eb6cee499d19fc9204e059ba37fc2dac32e2f25 Mon Sep 17 00:00:00 2001
From: Simon Riggs
Date: Fri, 7 Dec 2012 12:59:05 +0000
Subject: Clarify that COPY FREEZE is not a hard rule. Remove message when
 FREEZE not honoured, clarify reasons in comments and docs.

---
 doc/src/sgml/ref/copy.sgml | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

(limited to 'doc/src/sgml')

diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index 6d34c319888..6a0fabc978d 100644
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -186,17 +186,19 @@ COPY { <replaceable class="parameter">table_name</replaceable> [ ( <replaceable
     <term><literal>FREEZE</literal></term>
     <listitem>
      <para>
-      Specifies copying the data with rows already frozen, just as they
+      Requests copying the data with rows already frozen, just as they
       would be after running the <command>VACUUM FREEZE</> command.
       This is intended as a performance option for initial data loading.
       Rows will be frozen only if the table being loaded has been created
       in the current subtransaction, there are no cursors open and there
       are no older snapshots held by this transaction. If those conditions
       are not met the command will continue without error though will not
-      freeze rows.
+      freeze rows. It is also possible in rare cases that the request
+      cannot be honoured for internal reasons, hence <literal>FREEZE</literal>
+      is more of a guideline than a hard rule.
      </para>
      <para>
-      Note that all sessions will immediately be able to see the data
+      Note that all other sessions will immediately be able to see the data
       once it has been successfully loaded. This violates the normal rules
       of MVCC visibility and by specifying this option the user acknowledges
       explicitly that this is understood.
-- 
cgit v1.2.3