Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
6efdd418
Commit
6efdd418
authored
Dec 14, 2003
by
Neil Conway
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix two typos in the documentation for PREPARE.
parent
fef0c834
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
8 deletions
+8
-8
doc/src/sgml/ref/prepare.sgml
doc/src/sgml/ref/prepare.sgml
+8
-8
No files found.
doc/src/sgml/ref/prepare.sgml
View file @
6efdd418
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/prepare.sgml,v 1.
9 2003/12/01 22:07:58 momjian
Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/prepare.sgml,v 1.
10 2003/12/14 00:55:46 neilc
Exp $
PostgreSQL documentation
-->
...
...
@@ -52,7 +52,7 @@ PREPARE <replaceable class="PARAMETER">plan_name</replaceable> [ (<replaceable c
</para>
<para>
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 <replaceable class="PARAMETER">plan_name</replaceable> [ (<replaceable c
<title>Notes</title>
<para>
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. <productname>PostgreSQL</productname> collects
statistics on the distribution of data in the table, and can use
constant values in a statement to make guesses about the likely
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment