mirror of
https://github.com/postgres/postgres.git
synced 2025-05-22 00:02:02 -04:00
Markup fixes.
Update for v6.5 release.
This commit is contained in:
Thomas G. Lockhart
parent
7d831b5379
commit
b805230906
@ -1,18 +1,37 @@
|
||||
<Sect1>
|
||||
<Title>About This Release</Title>
|
||||
<sect1 id="about">
|
||||
<title>About This Release</title>
|
||||
|
||||
<Para>
|
||||
<ProductName>PostgreSQL</ProductName> is available without cost. This manual
|
||||
describes version 6.4 of <ProductName>PostgreSQL</ProductName>.
|
||||
</Para>
|
||||
<Para>
|
||||
We will use <ProductName>Postgres</ProductName>
|
||||
to mean the version distributed as <ProductName>PostgreSQL</ProductName>.
|
||||
</Para>
|
||||
<Para>
|
||||
<para>
|
||||
<productname>PostgreSQL</productname> is available without cost. This manual
|
||||
describes version 6.5 of <productname>PostgreSQL</productname>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
We will use <productname>Postgres</productname>
|
||||
to mean the version distributed as <productname>PostgreSQL</productname>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Check the Administrator's Guide for a list of currently supported machines.
|
||||
In general,
|
||||
<ProductName>Postgres</ProductName> is portable to any Unix/Posix-compatible system
|
||||
<productname>Postgres</productname> is portable to any Unix/Posix-compatible system
|
||||
with full libc library support.
|
||||
</Para>
|
||||
</Sect1>
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<!-- Keep this comment at the end of the file
|
||||
Local variables:
|
||||
mode: sgml
|
||||
sgml-omittag:nil
|
||||
sgml-shorttag:t
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-always-quote-attributes:t
|
||||
sgml-indent-step:1
|
||||
sgml-indent-data:t
|
||||
sgml-parent-document:nil
|
||||
sgml-default-dtd-file:"./reference.ced"
|
||||
sgml-exposed-tags:nil
|
||||
sgml-local-catalogs:"/usr/lib/sgml/catalog"
|
||||
sgml-local-ecat-files:nil
|
||||
End:
|
||||
-->
|
||||
|
||||
@ -1,9 +1,13 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.14 1999/01/07 03:01:27 thomas Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.15 1999/05/27 15:49:07 thomas Exp $
|
||||
Documentation Guide
|
||||
Thomas Lockhart
|
||||
|
||||
$Log: docguide.sgml,v $
|
||||
Revision 1.15 1999/05/27 15:49:07 thomas
|
||||
Markup fixes.
|
||||
Update for v6.5 release.
|
||||
|
||||
Revision 1.14 1999/01/07 03:01:27 thomas
|
||||
Fix column formatting for a table. No content changes.
|
||||
|
||||
@ -42,7 +46,7 @@ Include working list of all documentation sources, with current status
|
||||
|
||||
-->
|
||||
|
||||
<appendix label="A" Id="docguide">
|
||||
<appendix label="DG2" id="docguide">
|
||||
<docinfo>
|
||||
<authorgroup>
|
||||
<author>
|
||||
@ -54,7 +58,7 @@ Include working list of all documentation sources, with current status
|
||||
<surname>Helbekkmo</surname>
|
||||
</author>
|
||||
</authorgroup>
|
||||
<date>1998-04-28</date>
|
||||
<date>1999-05-27</date>
|
||||
</docinfo>
|
||||
|
||||
<title>Documentation</title>
|
||||
@ -94,7 +98,7 @@ Hardcopy, for in-depth reading and reference.
|
||||
|
||||
<para>
|
||||
<table tocentry="1">
|
||||
<title><ProductName>Postgres</ProductName> Documentation Products</title>
|
||||
<title><productname>Postgres</productname> Documentation Products</title>
|
||||
<tgroup cols="2">
|
||||
<thead>
|
||||
<row>
|
||||
@ -147,19 +151,20 @@ packages.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The documentation sources are written using <acronym>SGML</acronym>
|
||||
markup of plain text files.
|
||||
The purpose of <productname>DocBook</productname> <acronym>SGML</acronym>
|
||||
is to allow an author to
|
||||
specify the structure and content of a document (e.g. using the
|
||||
specify the structure and content of a technical document (using the
|
||||
<productname>DocBook</productname> <acronym>DTD</acronym>), and to
|
||||
have a document style define how that content is rendered into a
|
||||
final form (e.g. using Norm Walsh's
|
||||
<productname>Modular Style Sheets</productname>).</para>
|
||||
|
||||
|
||||
<para>
|
||||
See <ulink url="http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro.html">
|
||||
Introduction to DocBook</ulink> for a nice "quickstart" summary of
|
||||
DocBook features.
|
||||
See
|
||||
<ulink url="http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro.html">Introduction to DocBook</ulink>
|
||||
for a nice "quickstart" summary of DocBook features.
|
||||
<ulink url="http://www.ora.com/homepages/dtdparse/docbook/3.0/"> DocBook Elements</ulink>
|
||||
provides a powerful cross-reference for features of
|
||||
<productname>DocBook</productname>.
|
||||
@ -174,13 +179,12 @@ James Clark's
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Currently, hardcopy is produced by importing <firstterm>Rich Text
|
||||
Format</firstterm> (<acronym>RTF</acronym>) output from
|
||||
Currently, hardcopy is produced by importing
|
||||
<firstterm>Rich Text Format</firstterm> (<acronym>RTF</acronym>) output from
|
||||
<application>jade</application> into
|
||||
<productname>ApplixWare</productname> for minor formatting fixups then
|
||||
<productname>ApplixWare</productname> for minor formatting fixups, then
|
||||
exporting as a Postscript file.</para>
|
||||
|
||||
|
||||
<para>
|
||||
<ulink url="http://sunsite.unc.edu/pub/packages/TeX/systems/unix/">
|
||||
<productname>TeX</productname></ulink> is a supported format for
|
||||
@ -352,7 +356,7 @@ Too much tabular info and not very helpful in hardcopy.
|
||||
|
||||
<para>
|
||||
<table tocentry="1">
|
||||
<title><ProductName>Postgres</ProductName> Documentation Sources</title>
|
||||
<title><productname>Postgres</productname> Documentation Sources</title>
|
||||
<tgroup cols="3">
|
||||
<thead>
|
||||
<row>
|
||||
@ -526,7 +530,7 @@ Status
|
||||
|
||||
<para>
|
||||
<table tocentry="1">
|
||||
<title><ProductName>Postgres</ProductName> Documentation Sources</title>
|
||||
<title><productname>Postgres</productname> Documentation Sources</title>
|
||||
<tgroup cols="3">
|
||||
<thead>
|
||||
<row>
|
||||
@ -965,7 +969,7 @@ by typing
|
||||
</para></sect1>
|
||||
|
||||
<sect1>
|
||||
<title>Hardcopy Generation for v6.4</title>
|
||||
<title>Hardcopy Generation for v6.5</title>
|
||||
|
||||
<para>
|
||||
The hardcopy Postscript documentation is generated by converting the
|
||||
@ -975,6 +979,7 @@ After a little cleanup (see the following
|
||||
section) the output is "printed" to a postscript file.
|
||||
</para>
|
||||
|
||||
<!--
|
||||
<para>
|
||||
Some figures were redrawn to avoid having bitmap
|
||||
<acronym>GIF</acronym> files in the hardcopy documentation. One
|
||||
@ -988,6 +993,7 @@ following commands:
|
||||
</programlisting>
|
||||
|
||||
</para>
|
||||
-->
|
||||
|
||||
<sect2>
|
||||
<title><acronym>RTF</acronym> Cleanup Procedure</title>
|
||||
@ -1037,7 +1043,8 @@ Insert figures into the document. Center each figure on the page using
|
||||
the centering margins button.</para>
|
||||
|
||||
<para>
|
||||
Not all documents have figures. You can grep the <acronym>SGML</acronym> source files for
|
||||
Not all documents have figures.
|
||||
You can grep the <acronym>SGML</acronym> source files for
|
||||
the string <quote>Graphic</quote> to identify those parts of the
|
||||
documentation which may have figures. A few figures are replicated in
|
||||
various parts of the documentation.
|
||||
@ -1660,7 +1667,7 @@ Run <productname>texhash</productname> to update the tex database.
|
||||
<!-- Keep this comment at the end of the file
|
||||
Local variables:
|
||||
mode: sgml
|
||||
sgml-omittag:t
|
||||
sgml-omittag:nil
|
||||
sgml-shorttag:t
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-always-quote-attributes:t
|
||||
|
||||
@ -19,10 +19,10 @@
|
||||
Unlike most other database systems which use locks for concurrency control,
|
||||
<productname>Postgres</productname>
|
||||
maintains data consistency by using a multiversion model.
|
||||
This means that while querying database each transaction sees
|
||||
This means that while querying a database each transaction sees
|
||||
a snapshot of data (a <firstterm>database version</firstterm>)
|
||||
as it was some
|
||||
time ago, regardless of the current state of data queried.
|
||||
time ago, regardless of the current state of the underlying data.
|
||||
This protects the transaction from viewing inconsistent data that
|
||||
could be caused by (other) concurrent transaction updates on the same
|
||||
data rows, providing <firstterm>transaction isolation</firstterm>
|
||||
@ -87,81 +87,88 @@
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Accordingly, the four isolation levels are defined to be:
|
||||
The four isolation levels and the corresponding behaviors are described below.
|
||||
|
||||
<segmentedlist>
|
||||
<segtitle>
|
||||
Isolation Level
|
||||
</segtitle>
|
||||
<segtitle>
|
||||
<table tocentry="1">
|
||||
<title><productname>Postgres</productname> Isolation Levels</title>
|
||||
<titleabbrev>Isolation Levels</titleabbrev>
|
||||
<tgroup cols="4">
|
||||
<thead>
|
||||
<row>
|
||||
<entry>
|
||||
Dirty Read
|
||||
</segtitle>
|
||||
<segtitle>
|
||||
</entry>
|
||||
<entry>
|
||||
Non-Repeatable Read
|
||||
</segtitle>
|
||||
<segtitle>
|
||||
</entry>
|
||||
<entry>
|
||||
Phantom Read
|
||||
</segtitle>
|
||||
<seglistitem>
|
||||
<seg>
|
||||
</entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>
|
||||
Read uncommitted
|
||||
</seg>
|
||||
<seg>
|
||||
</entry>
|
||||
<entry>
|
||||
Possible
|
||||
</seg>
|
||||
<seg>
|
||||
</entry>
|
||||
<entry>
|
||||
Possible
|
||||
</seg>
|
||||
<seg>
|
||||
</entry>
|
||||
<entry>
|
||||
Possible
|
||||
</seg>
|
||||
</seglistitem>
|
||||
</entry>
|
||||
</row>
|
||||
|
||||
<seglistitem>
|
||||
<seg>
|
||||
<row>
|
||||
<entry>
|
||||
Read committed
|
||||
</seg>
|
||||
<seg>
|
||||
</entry>
|
||||
<entry>
|
||||
Not possible
|
||||
</seg>
|
||||
<seg>
|
||||
</entry>
|
||||
<entry>
|
||||
Possible
|
||||
</seg>
|
||||
<seg>
|
||||
</entry>
|
||||
<entry>
|
||||
Possible
|
||||
</seg>
|
||||
</seglistitem>
|
||||
</entry>
|
||||
</row>
|
||||
|
||||
<seglistitem>
|
||||
<seg>
|
||||
<row>
|
||||
<entry>
|
||||
Repeatable read
|
||||
</seg>
|
||||
<seg>
|
||||
</entry>
|
||||
<entry>
|
||||
Not possible
|
||||
</seg>
|
||||
<seg>
|
||||
</entry>
|
||||
<entry>
|
||||
Not possible
|
||||
</seg>
|
||||
<seg>
|
||||
</entry>
|
||||
<entry>
|
||||
Possible
|
||||
</seg>
|
||||
</seglistitem>
|
||||
</entry>
|
||||
</row>
|
||||
|
||||
<seglistitem>
|
||||
<seg>
|
||||
<row>
|
||||
<entry>
|
||||
Serializable
|
||||
</seg>
|
||||
<seg>
|
||||
</entry>
|
||||
<entry>
|
||||
Not possible
|
||||
</seg>
|
||||
<seg>
|
||||
</entry>
|
||||
<entry>
|
||||
Not possible
|
||||
</seg>
|
||||
<seg>
|
||||
</entry>
|
||||
<entry>
|
||||
Not possible
|
||||
</seg>
|
||||
</seglistitem>
|
||||
</segmentedlist>
|
||||
</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
<productname>Postgres</productname>
|
||||
offers the read committed and serializable isolation levels.
|
||||
@ -172,7 +179,8 @@
|
||||
<title>Read Committed Isolation Level</title>
|
||||
|
||||
<para>
|
||||
This is the default isolation level in <productname>Postgres</productname>.
|
||||
<firstterm>Read Committed</firstterm>
|
||||
is the default isolation level in <productname>Postgres</productname>.
|
||||
When a transaction runs on this isolation level, a query sees only
|
||||
data committed before the query began and never sees either dirty data or
|
||||
concurrent transaction changes committed during query execution.
|
||||
@ -196,7 +204,8 @@
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Note that the results of execution of SELECT or INSERT (with a query)
|
||||
Note that the results of execution of <command>SELECT</command>
|
||||
or <command>INSERT</command> (with a query)
|
||||
statements will not be affected by concurrent transactions.
|
||||
</para>
|
||||
</sect1>
|
||||
@ -205,8 +214,9 @@
|
||||
<title>Serializable Isolation Level</title>
|
||||
|
||||
<para>
|
||||
This level provides the highest transaction isolation. When a
|
||||
transaction is on the <firstterm>serializable</firstterm> level,
|
||||
<firstterm>Serializable</firstterm> provides the highest transaction isolation.
|
||||
When a
|
||||
transaction is on the serializable level,
|
||||
a query sees only data
|
||||
committed before the transaction began and never see either dirty data
|
||||
or concurrent transaction changes committed during transaction
|
||||
@ -216,8 +226,9 @@
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If a row returned by query while executing
|
||||
<command>UPDATE</command>/<command>DELETE</command>/<command>SELECT FOR UPDATE</command>
|
||||
If a row returned by query while executing a
|
||||
<command>UPDATE</command>
|
||||
(or <command>DELETE</command> or <command>SELECT FOR UPDATE</command>)
|
||||
statement is being updated by
|
||||
a concurrent uncommitted transaction then the second transaction
|
||||
that tries to update this row will wait for the other transaction to
|
||||
@ -394,8 +405,8 @@ ERROR: Can't serialize access due to concurrent update
|
||||
|
||||
<note>
|
||||
<para>
|
||||
Note that only AccessExclusiveLock blocks <command>SELECT</command> (without FOR
|
||||
UPDATE) statement.
|
||||
Only AccessExclusiveLock blocks <command>SELECT</command> (without
|
||||
<option>FOR UPDATE</option>) statement.
|
||||
</para>
|
||||
</note>
|
||||
</para>
|
||||
@ -409,11 +420,11 @@ ERROR: Can't serialize access due to concurrent update
|
||||
<title>Row-level locks</title>
|
||||
|
||||
<para>
|
||||
These locks are acquired by means of modification of internal
|
||||
fields of row being updated/deleted/marked for update.
|
||||
These locks are acquired when internal
|
||||
fields of a row are being updated (or deleted or marked for update).
|
||||
<productname>Postgres</productname>
|
||||
doesn't remember any information about modified rows in memory and
|
||||
so hasn't limit for locked rows without lock escalation.
|
||||
so has no limit to the number of rows locked without lock escalation.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@ -434,7 +445,8 @@ ERROR: Can't serialize access due to concurrent update
|
||||
<para>
|
||||
Though <productname>Postgres</productname>
|
||||
provides unblocking read/write access to table
|
||||
data, it is not the case for all index access methods implemented
|
||||
data, unblocked read/write access is not provided for every
|
||||
index access methods implemented
|
||||
in <productname>Postgres</productname>.
|
||||
</para>
|
||||
|
||||
@ -448,7 +460,7 @@ ERROR: Can't serialize access due to concurrent update
|
||||
</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Share/exclusive INDEX-level locks are used for read/write access.
|
||||
Share/exclusive index-level locks are used for read/write access.
|
||||
Locks are released after statement is done.
|
||||
</para>
|
||||
</listitem>
|
||||
@ -460,7 +472,7 @@ ERROR: Can't serialize access due to concurrent update
|
||||
</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Share/exclusive PAGE-level locks are used for read/write access.
|
||||
Share/exclusive page-level locks are used for read/write access.
|
||||
Locks are released after page is processed.
|
||||
</para>
|
||||
|
||||
@ -477,13 +489,13 @@ ERROR: Can't serialize access due to concurrent update
|
||||
</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Short-term share/exclusive PAGE-level latches are used for
|
||||
Short-term share/exclusive page-level latches are used for
|
||||
read/write access. Latches are released immediately after the index
|
||||
tuple is inserted/fetched.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Btree indices provide highest concurrency without deadlock
|
||||
Btree indices provide the highest concurrency without deadlock
|
||||
conditions.
|
||||
</para>
|
||||
</listitem>
|
||||
@ -503,8 +515,8 @@ ERROR: Can't serialize access due to concurrent update
|
||||
by <command>SELECT</command> it doesn't mean that this row really
|
||||
exists at the time it is returned (i.e. sometime after the
|
||||
statement or transaction began) nor
|
||||
that the row is protected from deletion/updation by concurrent
|
||||
transactions before the current transaction commit or rollback.
|
||||
that the row is protected from deletion or update by concurrent
|
||||
transactions before the current transaction does a commit or rollback.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
||||
@ -100,7 +100,7 @@ or will have no leading prompt, depending on the context.
|
||||
|
||||
<note>
|
||||
<para>
|
||||
At the time of writing (<Productname>Postgres</Productname> v6.4) the notation for
|
||||
At the time of writing (<Productname>Postgres</Productname> v6.5) the notation for
|
||||
flagging commands is not universally consistant throughout the documentation set.
|
||||
Please report problems to
|
||||
<ulink url="mailto:docs@postgresql.org">the Documentation Mailing List</ulink>.
|
||||
@ -108,3 +108,20 @@ Please report problems to
|
||||
</note>
|
||||
|
||||
</sect1>
|
||||
|
||||
<!-- Keep this comment at the end of the file
|
||||
Local variables:
|
||||
mode: sgml
|
||||
sgml-omittag:nil
|
||||
sgml-shorttag:t
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-always-quote-attributes:t
|
||||
sgml-indent-step:1
|
||||
sgml-indent-data:t
|
||||
sgml-parent-document:nil
|
||||
sgml-default-dtd-file:"./reference.ced"
|
||||
sgml-exposed-tags:nil
|
||||
sgml-local-catalogs:"/usr/lib/sgml/catalog"
|
||||
sgml-local-ecat-files:nil
|
||||
End:
|
||||
-->
|
||||
|
||||
@ -1,11 +1,15 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.24 1999/05/26 17:30:29 thomas Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.25 1999/05/27 15:49:08 thomas Exp $
|
||||
|
||||
Postgres integrated documentation.
|
||||
Other subset docs should be copied and shrunk from here.
|
||||
thomas 1998-02-23
|
||||
|
||||
$Log: postgres.sgml,v $
|
||||
Revision 1.25 1999/05/27 15:49:08 thomas
|
||||
Markup fixes.
|
||||
Update for v6.5 release.
|
||||
|
||||
Revision 1.24 1999/05/26 17:30:29 thomas
|
||||
Add chapters on CVS access, MVCC, SQL theory to the docs.
|
||||
Add an appendix with more details on date/time attributes and handling.
|
||||
@ -126,6 +130,7 @@ Move SQL reference pages up into the User's Guide.
|
||||
<!entity install SYSTEM "install.sgml">
|
||||
<!entity installw SYSTEM "install-win32.sgml">
|
||||
<!entity intro-ag SYSTEM "intro-ag.sgml">
|
||||
<!entity layout SYSTEM "layout.sgml">
|
||||
<!entity ports SYSTEM "ports.sgml">
|
||||
<!entity runtime SYSTEM "runtime.sgml">
|
||||
<!entity recovery SYSTEM "recovery.sgml">
|
||||
@ -291,6 +296,7 @@ Your name here...
|
||||
&intro-ag;
|
||||
&ports;
|
||||
&config;
|
||||
&layout;
|
||||
&install;
|
||||
&installw;
|
||||
&runtime;
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<sect1>
|
||||
<sect1 id="y2k">
|
||||
<title>Y2K Statement</title>
|
||||
|
||||
<note>
|
||||
@ -59,7 +59,6 @@ current time" may propagate into apparent Y2K problems in
|
||||
<productname>Postgres</productname>.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
<para>
|
||||
@ -72,3 +71,20 @@ for further discussion of Y2K issues, particularly
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<!-- Keep this comment at the end of the file
|
||||
Local variables:
|
||||
mode: sgml
|
||||
sgml-omittag:nil
|
||||
sgml-shorttag:t
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-always-quote-attributes:t
|
||||
sgml-indent-step:1
|
||||
sgml-indent-data:t
|
||||
sgml-parent-document:nil
|
||||
sgml-default-dtd-file:"./reference.ced"
|
||||
sgml-exposed-tags:nil
|
||||
sgml-local-catalogs:"/usr/lib/sgml/catalog"
|
||||
sgml-local-ecat-files:nil
|
||||
End:
|
||||
-->
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user