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
b05204ac
Commit
b05204ac
authored
22 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
Fix some minor grammatical errors.
parent
9392c405
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/perform.sgml
+4
-4
4 additions, 4 deletions
doc/src/sgml/perform.sgml
with
4 additions
and
4 deletions
doc/src/sgml/perform.sgml
+
4
−
4
View file @
b05204ac
<!--
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/perform.sgml,v 1.2
2
200
2/11/11 20:14:03 petere
Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/perform.sgml,v 1.2
3
200
3/01/12 18:42:59 tgl
Exp $
-->
-->
<chapter id="performance-tips">
<chapter id="performance-tips">
...
@@ -600,7 +600,7 @@ SELECT * FROM a, b, c WHERE a.id = b.id AND b.ref = c.id;
...
@@ -600,7 +600,7 @@ SELECT * FROM a, b, c WHERE a.id = b.id AND b.ref = c.id;
SELECT * FROM a CROSS JOIN b CROSS JOIN c WHERE a.id = b.id AND b.ref = c.id;
SELECT * FROM a CROSS JOIN b CROSS JOIN c WHERE a.id = b.id AND b.ref = c.id;
SELECT * FROM a JOIN (b JOIN c ON (b.ref = c.id)) ON (a.id = b.id);
SELECT * FROM a JOIN (b JOIN c ON (b.ref = c.id)) ON (a.id = b.id);
</programlisting>
</programlisting>
but
the second and third take less time to plan than the first. This effect
the second and third take less time to plan than the first. This effect
is not worth worrying about for only three tables, but it can be a
is not worth worrying about for only three tables, but it can be a
lifesaver with many tables.
lifesaver with many tables.
</para>
</para>
...
@@ -628,8 +628,8 @@ SELECT * FROM d LEFT JOIN
...
@@ -628,8 +628,8 @@ SELECT * FROM d LEFT JOIN
(SELECT * FROM a, b, c WHERE ...) AS ss
(SELECT * FROM a, b, c WHERE ...) AS ss
ON (...);
ON (...);
</programlisting>
</programlisting>
Here, joining D must be the last step in the query plan, but the
Here, joining
to
D must be the last step in the query plan, but the
planner is free to consider various join orders for A, B, C.
planner is free to consider various join orders for A, B,
and
C.
</para>
</para>
<para>
<para>
...
...
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