706a32cdf6
Big editing for consistent content and presentation.
2003-03-13 01:30:29 +00:00
f21fb30dfc
Revert optimizer page count change.
2003-01-28 03:34:29 +00:00
9b9b14915b
Fix typo 233 pages -> 333 pages.
2003-01-27 22:40:56 +00:00
9f5f212475
Allow the planner to collapse explicit inner JOINs together, rather than
...
necessarily following the JOIN syntax to develop the query plan. The old
behavior is still available by setting GUC variable JOIN_COLLAPSE_LIMIT
to 1. Also create a GUC variable FROM_COLLAPSE_LIMIT to control the
similar decision about when to collapse sub-SELECT lists into their parent
lists. (This behavior existed already, but the limit was always
GEQO_THRESHOLD/2; now it's separately adjustable.)
2003-01-25 23:10:30 +00:00
b05204ac8a
Fix some minor grammatical errors.
2003-01-12 18:42:59 +00:00
1b342df00a
Merge documentation updates from 7.3 branch.
2002-11-11 20:14:04 +00:00
bc49968764
Add more appropriate markup.
2002-09-21 18:32:54 +00:00
ea10ec1b69
Tweak labeling of plan qual conditions for more consistency.
2002-03-24 17:11:37 +00:00
10d3995057
EXPLAIN output now comes out as a query result, not a NOTICE message.
...
Also, fix debug logging of parse/plan trees so that the messages actually
go through elog(), not directly to stdout.
2002-03-24 04:31:09 +00:00
b6ea172ace
Spell checking and markup additions
2002-03-22 19:20:45 +00:00
92b1ab75d4
Update docs for new INFO, NOTICE, WARNING elog() levels.
2002-03-06 06:44:33 +00:00
bf43bed848
Spell-check and markup police
2002-01-20 22:19:57 +00:00
651a639b8b
proof-reading
2001-11-28 20:49:10 +00:00
2475e87481
Deprecate 'current' for date/time input.
...
Fix up references to "PostgreSQL" rather than "Postgres". Was roughly
evenly split between the two before. ref/ files not yet done.
2001-11-21 05:53:41 +00:00
2bb6b98d5c
Add a section about the planner's statistics, including a description
...
of the new pg_stats view.
2001-10-16 01:13:44 +00:00
705869dd17
Uppercase keywords where appropriate.
2001-10-12 23:32:34 +00:00
ffb8f73890
Bunch of copy fitting and style sheet tweakage to get decent looking print
...
output (from pdfjadetex). Also updated instructions to install documentation
processing toolchain.
2001-10-09 18:46:00 +00:00
89fa551808
EXPLAIN ANALYZE feature to measure and show actual runtimes and tuple
...
counts alongside the planner's estimates. By Martijn van Oosterhout,
with some further work by Tom Lane.
2001-09-18 01:59:07 +00:00
351a0c1736
Replace ASCII-quotes with proper markup.
2001-09-13 15:55:24 +00:00
84956e71a3
Markup additions and spell check. (covers User's Guide)
2001-09-09 17:21:59 +00:00
7d6e28149e
Mention that EXPLAIN results on small tables shouldn't be extrapolated
...
to large tables. Recommend ANALYZE or VACUUM ANALYZE after populating
a table.
2001-06-22 18:53:36 +00:00
88ba401879
Update EXPLAIN discussion and examples to match current sources.
2001-06-11 00:52:09 +00:00
a6677f0f9e
Change "indices" to "indexes", per OED.
2001-05-17 21:50:18 +00:00
6cda3ad8fe
Cause planner to make use of average-column-width statistic that is now
...
collected by ANALYZE. Also, add some modest amount of intelligence to
guesses that are used for varlena columns in the absence of any ANALYZE
statistics. The 'width' reported by EXPLAIN is finally something less
than totally bogus for varlena columns ... and, in consequence, hashjoin
estimating should be a little better ...
2001-05-09 00:35:09 +00:00
0967057b5d
minor copy editing
2001-03-24 23:03:26 +00:00
a276392e52
Update example of partially constraining join order to use a subselect
...
in FROM instead of an auxiliary view. We didn't have subselect-in-FROM
when I wrote this originally...
2001-02-19 00:24:30 +00:00
ad4fd77a5f
Restructure performance tips into a single chapter ('populating a
...
database' was way too small to make a chapter). Add a section about
using JOIN syntax to direct the planner.
2000-12-16 02:29:36 +00:00
Peter Eisentraut
Bruce Momjian
Tom Lane
Thomas G. Lockhart