From 6efdd4186c06171c67e5bbd709e45bee989b1059 Mon Sep 17 00:00:00 2001 From: Neil Conway Date: Sun, 14 Dec 2003 00:55:46 +0000 Subject: [PATCH] Fix two typos in the documentation for PREPARE. --- doc/src/sgml/ref/prepare.sgml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/doc/src/sgml/ref/prepare.sgml b/doc/src/sgml/ref/prepare.sgml index 684b4bb8ba..e7190b1b17 100644 --- a/doc/src/sgml/ref/prepare.sgml +++ b/doc/src/sgml/ref/prepare.sgml @@ -1,5 +1,5 @@ @@ -52,7 +52,7 @@ PREPARE plan_name [ ( - Prepared statements are only for the duration of the current + Prepared statements only last for the duration of the current database session. When the session ends, the prepared statement is forgotten, so it must be recreated before being used again. This also means that a single prepared statement cannot be used by @@ -115,12 +115,12 @@ PREPARE plan_name [ (Notes - In some situations, the query plan produced by for a prepared - statement may be inferior to the plan produced if the statement - were submitted and executed normally. This is because when the - statement is planned and the planner attempts to determine the - optimal query plan, the actual values of any parameters specified - in the statement are + In some situations, the query plan produced for a prepared + statement will be inferior to the query plan that would have been + chosen if the statement had been submitted and executed + normally. This is because when the statement is planned and the + planner attempts to determine the optimal query plan, the actual + values of any parameters specified in the statement are unavailable. PostgreSQL collects statistics on the distribution of data in the table, and can use constant values in a statement to make guesses about the likely