Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
6efdd418
Commit
6efdd418
authored
21 years ago
by
Neil Conway
Browse files
Options
Downloads
Patches
Plain Diff
Fix two typos in the documentation for PREPARE.
parent
fef0c834
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/ref/prepare.sgml
+8
-8
8 additions, 8 deletions
doc/src/sgml/ref/prepare.sgml
with
8 additions
and
8 deletions
doc/src/sgml/ref/prepare.sgml
+
8
−
8
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
PostgreSQL documentation
-->
-->
...
@@ -52,7 +52,7 @@ PREPARE <replaceable class="PARAMETER">plan_name</replaceable> [ (<replaceable c
...
@@ -52,7 +52,7 @@ PREPARE <replaceable class="PARAMETER">plan_name</replaceable> [ (<replaceable c
</para>
</para>
<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
database session. When the session ends, the prepared statement is
forgotten, so it must be recreated before being used again. This
forgotten, so it must be recreated before being used again. This
also means that a single prepared statement cannot be used by
also means that a single prepared statement cannot be used by
...
@@ -115,12 +115,12 @@ PREPARE <replaceable class="PARAMETER">plan_name</replaceable> [ (<replaceable c
...
@@ -115,12 +115,12 @@ PREPARE <replaceable class="PARAMETER">plan_name</replaceable> [ (<replaceable c
<title>Notes</title>
<title>Notes</title>
<para>
<para>
In some situations, the query plan produced
by
for a prepared
In some situations, the query plan produced for a prepared
statement
may
be inferior to the
plan produced if the statem
en
t
statement
will
be inferior to the
query plan that would have be
en
were submitted and executed normally. This is because when the
chosen if the statement had been submitted and executed
statement is planned and the planner attempts to determine
the
normally. This is because when the statement is planned and
the
optimal query plan, the actual values of any parameters specified
planner attempts to determine the optimal query plan, the actual
in the statement are
values of any parameters specified
in the statement are
unavailable. <productname>PostgreSQL</productname> collects
unavailable. <productname>PostgreSQL</productname> collects
statistics on the distribution of data in the table, and can use
statistics on the distribution of data in the table, and can use
constant values in a statement to make guesses about the likely
constant values in a statement to make guesses about the likely
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment