0add759825
More minor updates and copy-editing.
2004-12-23 23:07:38 +00:00
5374d097de
Change planner to use the current true disk file size as its estimate of
...
a relation's number of blocks, rather than the possibly-obsolete value
in pg_class.relpages. Scale the value in pg_class.reltuples correspondingly
to arrive at a hopefully more accurate number of rows. When pg_class
contains 0/0, estimate a tuple width from the column datatypes and divide
that into current file size to estimate number of rows. This improved
methodology allows us to jettison the ancient hacks that put bogus default
values into pg_class when a table is first created. Also, per a suggestion
from Simon, make VACUUM (but not VACUUM FULL or ANALYZE) adjust the value
it puts into pg_class.reltuples to try to represent the mean tuple density
instead of the minimal density that actually prevails just after VACUUM.
These changes alter the plans selected for certain regression tests, so
update the expected files accordingly. (I removed join_1.out because
it's not clear if it still applies; we can add back any variant versions
as they are shown to be needed.)
2004-12-01 19:00:56 +00:00
ec7a6bd9a2
Replace "--" and "---" with "—" as appropriate, for better-looking
...
output.
2004-11-15 06:32:15 +00:00
92b0b080eb
Add an index entry for "Performance Tips". Patch from Alvaro Herrera.
2004-05-27 01:00:40 +00:00
0fa2afa93a
Make psql's \d+ command indicate whether the table in question
...
contains OIDs. Also, minor documentation improvements to the
psql reference page.
2004-04-22 17:38:16 +00:00
2ff4e44043
Improvements to the backup & restore documentation.
2004-04-22 07:02:36 +00:00
7a944e41b4
Convert some GUC variable references to links.
2004-03-25 18:57:57 +00:00
80ec228389
Refer to GUC variables using <xref> tags rather than <varname> tags,
...
where appropriate. Add "id" and "xreflabel" tags to the descriptions
of the GUC variables to facilitate this. Also make a few minor docs
cleanups.
2004-03-09 16:57:47 +00:00
391c3811a2
Rename SortMem and VacuumMem to work_mem and maintenance_work_mem.
...
Make btree index creation and initial validation of foreign-key constraints
use maintenance_work_mem rather than work_mem as their memory limit.
Add some code to guc.c to allow these variables to be referenced by their
old names in SHOW and SET commands, for backwards compatibility.
2004-02-03 17:34:04 +00:00
024f3fa52f
Minor documentation improvements.
2004-01-11 05:46:58 +00:00
0b52062265
This patch makes some improvements and adds some additional detail
...
to the documentation on routine database maintainence activities.
I also corrected a bunch of SGML markup.
2003-12-14 00:10:32 +00:00
969685ad44
$Header: -> $PostgreSQL Changes ...
2003-11-29 19:52:15 +00:00
8442a92e5a
Spell checking, consistent terminology.
2003-11-01 01:56:29 +00:00
0a4048646b
Document all the system views created by initdb (several of these were
...
never documented anywhere, sigh). Centralize the detailed documentation
of system views into catalogs.sgml, and provide cross-references.
2003-10-17 22:38:20 +00:00
fe1b5034dd
Adjust display of actual runtimes in EXPLAIN output to use three fractional
...
digits, and label it 'ms' not 'msec', for consistency with psql's \timing
display. Per recent discussions.
2003-10-17 01:14:26 +00:00
8087446b14
> That's a fairly useless place to put it, though, since someone would
...
> only think to look at sort_mem if they already had a clue. It should
> be mentioned under bulk data load (in performance tips chapter)
Attached is a doc patch that does this. The way I've worded it may not
be the best, though.
Neil Conway
2003-10-10 02:08:42 +00:00
188eda0df2
Consistenly lowercase GUC variable names, in docs and error messages.
2003-09-11 18:30:39 +00:00
8e27be4310
This patch makes a few minor improvements to the docs: make the
...
<varname> conventions more consistent, and improve the ANALYZE ref page.
Neil Conway
2003-09-11 17:31:45 +00:00
c326d8f4f2
Add/edit index entries.
2003-08-31 17:32:24 +00:00
ebbd2edf82
Seems the runtime.sgml and perform.sgml patches combined are
...
incompatible.
I believe the attached xref meets the intent of the perform.sgml change.
--
Rod Taylor <rbt@rbt.ca>
2003-06-25 02:07:33 +00:00
7cb4278e82
Small patch to link to the proper place in the "runtime" file,
...
and to add the "schemaname" column to the description of the
pg_stats view.
Greg Sabino Mullane
2003-06-24 23:19:11 +00:00
5e5c5cd31a
Merge documentation into one book. (Build with "make html".) Replace
...
vague cross-references with real links.
2003-03-25 16:15:44 +00:00
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
Tom Lane
Neil Conway
PostgreSQL Daemon
Peter Eisentraut
Bruce Momjian
Thomas G. Lockhart