database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-21 12:05:57 +03:00
Code

Update FAQ.

Browse Source
This commit is contained in:
Bruce Momjian 2002-03-03 16:02:31 +00:00
parent 343e47c27d
commit 592caa0897
2 changed files with 69 additions and 63 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
doc/FAQ
View File

@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Tue Feb 26 23:52:13 EST 2002 Last updated: Sun Mar 3 11:02:16 EST 2002
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@ -706,28 +706,30 @@
4.8) My queries are slow or don't make use of the indexes. Why? 4.8) My queries are slow or don't make use of the indexes. Why?
PostgreSQL does not automatically maintain statistics. VACUUM must be Indexes are not automatically used by every query. Indexes are only
run to update the statistics. After statistics are updated, the used if the table is larger than a minimum size, and the index selects
optimizer knows how many rows in the table, and can better decide if only a small percentage of the rows in the table. This is because the
it should use indexes. Note that the optimizer does not use indexes in random disk access caused by an index scan is sometimes slower than a
cases when the table is small because a sequential scan would be straight read through the table, or sequential scan.
faster.
For column-specific optimization statistics, use VACUUM ANALYZE. To determine if an index should be used, PostgreSQL must have
VACUUM ANALYZE is important for complex multijoin queries, so the statistics about the table. These statistics are collected using
optimizer can estimate the number of rows returned from each table, VACUUM ANALYZE, or simply ANALYZE. Using statistics, the optimizer
and choose the proper join order. The backend does not keep track of knows how many rows are in the table, and can better determine if
column statistics on its own, so VACUUM ANALYZE must be run to collect indexes should be used. Statistics are also valuable in determining
them periodically. optimal join order and join methods. Statistics collection should be
performed periodically as the contents of the table change.
Indexes are usually not used for ORDER BY or joins. A sequential scan Indexes are normally not used for ORDER BY or to perform joins. A
followed by an explicit sort is faster than an indexscan of all tuples sequential scan followed by an explicit sort is usually faster than an
of a large table. This is because random disk access is very slow. index scan of a large table.
However, LIMIT combined with ORDER BY often will use an index because
only a small portion of the table is returned.
When using wild-card operators such as LIKE or ~, indexes can only be When using wild-card operators such as LIKE or ~, indexes can only be
used if the beginning of the search is anchored to the start of the used if the beginning of the search is anchored to the start of the
string. So, to use indexes, LIKE searches should not begin with %, and string. Therefore, to use indexes, LIKE patterns must not start with
~(regular expression searches) should start with ^. %, and ~(regular expression) patterns must start with ^.
4.9) How do I see how the query optimizer is evaluating my query? 4.9) How do I see how the query optimizer is evaluating my query?

94
doc/src/FAQ/FAQ.html
View File

@ -14,7 +14,7 @@
alink="#0000ff"> alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
<P>Last updated: Tue Feb 26 23:52:13 EST 2002</P> <P>Last updated: Sun Mar 3 11:02:16 EST 2002</P>
<P>Current maintainer: Bruce Momjian (<A href= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR> "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@ -72,7 +72,8 @@
get <I>IpcMemoryCreate</I> errors. Why?<BR> get <I>IpcMemoryCreate</I> errors. Why?<BR>
<A href="#3.4">3.4</A>) When I try to start <I>postmaster</I>, I <A href="#3.4">3.4</A>) When I try to start <I>postmaster</I>, I
get <I>IpcSemaphoreCreate</I> errors. Why?<BR> get <I>IpcSemaphoreCreate</I> errors. Why?<BR>
<A href="#3.5">3.5</A>) How do I control connections from other hosts?<BR> <A href="#3.5">3.5</A>) How do I control connections from other
hosts?<BR>
<A href="#3.6">3.6</A>) How do I tune the database engine for <A href="#3.6">3.6</A>) How do I tune the database engine for
better performance?<BR> better performance?<BR>
<A href="#3.7">3.7</A>) What debugging features are available?<BR> <A href="#3.7">3.7</A>) What debugging features are available?<BR>
@ -116,9 +117,9 @@
<SMALL>SERIAL</SMALL> insert?<BR> <SMALL>SERIAL</SMALL> insert?<BR>
<A href="#4.15.3">4.15.3</A>) Don't <I>currval()</I> and <A href="#4.15.3">4.15.3</A>) Don't <I>currval()</I> and
<I>nextval()</I> lead to a race condition with other users?<BR> <I>nextval()</I> lead to a race condition with other users?<BR>
<A href="#4.15.4">4.15.4</A>) Why aren't my sequence numbers reused <A href="#4.15.4">4.15.4</A>) Why aren't my sequence numbers
on transaction abort? Why are there gaps in the numbering of my reused on transaction abort? Why are there gaps in the numbering of
sequence/SERIAL column?<BR> my sequence/SERIAL column?<BR>
<A href="#4.16">4.16</A>) What is an <SMALL>OID</SMALL>? What is a <A href="#4.16">4.16</A>) What is an <SMALL>OID</SMALL>? What is a
<SMALL>TID</SMALL>?<BR> <SMALL>TID</SMALL>?<BR>
<A href="#4.17">4.17</A>) What is the meaning of some of the terms <A href="#4.17">4.17</A>) What is the meaning of some of the terms
@ -213,9 +214,9 @@
UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE,
SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.</P> SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.</P>
<P>The above is the BSD license, the classic open-source license. It <P>The above is the BSD license, the classic open-source license.
has no restrictions on how the source code may be used. We like it It has no restrictions on how the source code may be used. We like
and have no intention of changing it.</P> it and have no intention of changing it.</P>
<H4><A name="1.3">1.3</A>) What Unix platforms does PostgreSQL run <H4><A name="1.3">1.3</A>) What Unix platforms does PostgreSQL run
on?</H4> on?</H4>
@ -326,9 +327,11 @@
"http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A> "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A>
and <A href= and <A href=
"http://www.commandprompt.com/ppbook/">http://www.commandprompt.com/ppbook/</A>. "http://www.commandprompt.com/ppbook/">http://www.commandprompt.com/ppbook/</A>.
There is a list of PostgreSQL books available for purchase at <A href= There is a list of PostgreSQL books available for purchase at <A
href=
"http://www.postgresql.org/books/">http://www.postgresql.org/books/</A>. "http://www.postgresql.org/books/">http://www.postgresql.org/books/</A>.
There is also a collection of PostgreSQL technical articles at <A href= There is also a collection of PostgreSQL technical articles at <A
href=
"http://techdocs.postgresql.org/">http://techdocs.postgresql.org/</A>.</P> "http://techdocs.postgresql.org/">http://techdocs.postgresql.org/</A>.</P>
<P><I>psql</I> has some nice \d commands to show information about <P><I>psql</I> has some nice \d commands to show information about
@ -348,9 +351,9 @@
<P>The PostgreSQL book at <A href= <P>The PostgreSQL book at <A href=
"http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A> "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A>
teaches <SMALL>SQL</SMALL>. There is another PostgreSQL book at teaches <SMALL>SQL</SMALL>. There is another PostgreSQL book at <A
<A href="http://www.commandprompt.com/ppbook/"> href=
http://www.commandprompt.com/ppbook.</A> "http://www.commandprompt.com/ppbook/">http://www.commandprompt.com/ppbook.</A>
There is a nice tutorial at <A href= There is a nice tutorial at <A href=
"http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm,</A> "http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm,</A>
at <A href= at <A href=
@ -856,14 +859,14 @@
<H4><A name="4.6">4.6</A>) How much database disk space is required <H4><A name="4.6">4.6</A>) How much database disk space is required
to store data from a typical text file?</H4> to store data from a typical text file?</H4>
<P>A PostgreSQL database may require up to five times the disk space <P>A PostgreSQL database may require up to five times the disk
to store data from a text file.</P> space to store data from a text file.</P>
<P>As an example, consider a file of 100,000 lines with an integer <P>As an example, consider a file of 100,000 lines with an integer
and text description on each line. Suppose the text string avergages and text description on each line. Suppose the text string
twenty bytes in length. The flat file would be 2.8 MB. The size avergages twenty bytes in length. The flat file would be 2.8 MB.
of the PostgreSQL database file containing this data can be The size of the PostgreSQL database file containing this data can
estimated as 6.4 MB:</P> be estimated as 6.4 MB:</P>
<PRE> <PRE>
36 bytes: each row header (approximate) 36 bytes: each row header (approximate)
24 bytes: one int field and one text filed 24 bytes: one int field and one text filed
@ -899,33 +902,33 @@
<H4><A name="4.8">4.8</A>) My queries are slow or don't make use of <H4><A name="4.8">4.8</A>) My queries are slow or don't make use of
the indexes. Why?</H4> the indexes. Why?</H4>
Indexes are not automatically used by every query. Indexes are only
used if the table is larger than a minimum size, and the index
selects only a small percentage of the rows in the table. This is
because the random disk access caused by an index scan is sometimes
slower than a straight read through the table, or sequential scan.
<P>PostgreSQL does not automatically maintain statistics. <P>To determine if an index should be used, PostgreSQL must have
V<SMALL>ACUUM</SMALL> must be run to update the statistics. After statistics about the table. These statistics are collected using
statistics are updated, the optimizer knows how many rows in the <SMALL>VACUUM ANALYZE</SMALL>, or simply <SMALL>ANALYZE</SMALL>.
table, and can better decide if it should use indexes. Note that Using statistics, the optimizer knows how many rows are in the
the optimizer does not use indexes in cases when the table is small table, and can better determine if indexes should be used.
because a sequential scan would be faster.</P> Statistics are also valuable in determining optimal join order and
join methods. Statistics collection should be performed
periodically as the contents of the table change.</P>
<P>For column-specific optimization statistics, use <SMALL>VACUUM <P>Indexes are normally not used for <SMALL>ORDER BY</SMALL> or to
ANALYZE.</SMALL> V<SMALL>ACUUM ANALYZE</SMALL> is important for perform joins. A sequential scan followed by an explicit sort is
complex multijoin queries, so the optimizer can estimate the number usually faster than an index scan of a large table.</P>
of rows returned from each table, and choose the proper join order. However, <SMALL>LIMIT</SMALL> combined with <SMALL>ORDER BY</SMALL>
The backend does not keep track of column statistics on its own, so often will use an index because only a small portion of the table
<SMALL>VACUUM ANALYZE</SMALL> must be run to collect them is returned.
periodically.</P>
<P>Indexes are usually not used for <SMALL>ORDER BY</SMALL> or
joins. A sequential scan followed by an explicit sort is faster
than an indexscan of all tuples of a large table. This is because
random disk access is very slow.</P>
<P>When using wild-card operators such as <SMALL>LIKE</SMALL> or <P>When using wild-card operators such as <SMALL>LIKE</SMALL> or
<I>~</I>, indexes can only be used if the beginning of the search <I>~</I>, indexes can only be used if the beginning of the search
is anchored to the start of the string. So, to use indexes, is anchored to the start of the string. Therefore, to use indexes,
<SMALL>LIKE</SMALL> searches should not begin with <I>%</I>, and <SMALL>LIKE</SMALL> patterns must not start with <I>%</I>, and
<I>~</I>(regular expression searches) should start with <I>~</I>(regular expression) patterns must start with <I>^</I>.</P>
<I>^</I>.</P>
<H4><A name="4.9">4.9</A>) How do I see how the query optimizer is <H4><A name="4.9">4.9</A>) How do I see how the query optimizer is
evaluating my query?</H4> evaluating my query?</H4>
@ -1091,13 +1094,14 @@ BYTEA bytea variable-length byte array (null-byte safe)
<P>No. Currval() returns the current value assigned by your <P>No. Currval() returns the current value assigned by your
backend, not by all users.</P> backend, not by all users.</P>
<H4><A name="4.15.4">4.15.4</A>) Why aren't my sequence numbers reused <H4><A name="4.15.4">4.15.4</A>) Why aren't my sequence numbers
on transaction abort? Why are there gaps in the numbering of my reused on transaction abort? Why are there gaps in the numbering of
sequence/SERIAL column?</H4> my sequence/SERIAL column?</H4>
<P>To improve concurrency, sequence values are given out to running <P>To improve concurrency, sequence values are given out to running
transactions as needed and are not locked until the transaction transactions as needed and are not locked until the transaction
completes. This causes gaps in numbering from aborted transactions. completes. This causes gaps in numbering from aborted
transactions.</P>
<H4><A name="4.16">4.16</A>) What is an <SMALL>OID</SMALL>? What is <H4><A name="4.16">4.16</A>) What is an <SMALL>OID</SMALL>? What is
a <SMALL>TID</SMALL>?</H4> a <SMALL>TID</SMALL>?</H4>