Skip to content

P
Postgres FD Implementation
Commit 0d2a78bf authored by Thomas G. Lockhart's avatar Thomas G. Lockhart
Browse files
Options

Repair markup to allow clean doc builds.

parent e7112784
Hide whitespace changes
Inline Side-by-side
Showing with 433 additions and 436 deletions
doc/src/sgml/advanced.sgml
View file @ 0d2a78bf
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.13 2000/06/09 01:43:55 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.14 2000/06/14 13:12:52 thomas Exp $
--> -->
<chapter id="advanced"> <chapter id="advanced">
...@@ -59,21 +59,22 @@ CREATE TABLE capitals ( ...@@ -59,21 +59,22 @@ CREATE TABLE capitals (
The inheritance hierarchy is a directed acyclic graph. The inheritance hierarchy is a directed acyclic graph.
</para> </para>
</note> </note>
</para>
<para> <para>
For example, the following query finds the names of all cities, For example, the following query finds the names of all cities,
including state capitals, that are located at an altitude including state capitals, that are located at an altitude
over 500ft, the query is: over 500ft, the query is:
<programlisting> <programlisting>
SELECT c.name, c.altitude SELECT c.name, c.altitude
FROM cities c FROM cities c
WHERE c.altitude > 500; WHERE c.altitude > 500;
</programlisting> </programlisting>
which returns: which returns:
<programlisting> <programlisting>
+----------+----------+ +----------+----------+
|name | altitude | |name | altitude |
+----------+----------+ +----------+----------+
...@@ -83,16 +84,16 @@ CREATE TABLE capitals ( ...@@ -83,16 +84,16 @@ CREATE TABLE capitals (
+----------+----------+ +----------+----------+
|Madison | 845 | |Madison | 845 |
+----------+----------+ +----------+----------+
</programlisting> </programlisting>
</para> </para>
<para> <para>
On the other hand, the following query finds On the other hand, the following query finds
all the cities, but not capital cities all the cities, but not capital cities
that are situated at an attitude of 500ft or higher: that are situated at an attitude of 500ft or higher:
<programlisting> <programlisting>
SELECT name, altitude SELECT name, altitude
FROM ONLY cities FROM ONLY cities
WHERE altitude &gt; 500; WHERE altitude &gt; 500;
...@@ -103,30 +104,34 @@ CREATE TABLE capitals ( ...@@ -103,30 +104,34 @@ CREATE TABLE capitals (
+----------+----------+ +----------+----------+
|Mariposa | 1953 | |Mariposa | 1953 |
+----------+----------+ +----------+----------+
</programlisting> </programlisting>
</para> </para>
<para>
Here the <quote>ONLY</quote> before cities indicates that the query should
be run over only cities and not classes below cities in the
inheritance hierarchy. Many of the commands that we
have already discussed -- <command>SELECT</command>,
<command>UPDATE</command> and <command>DELETE</command> --
support this <quote>ONLY</quote> notation.
</para>
Here the <quote>ONLY</quote> before cities indicates that the query should <para>
be run over only cities and not classes below cities in the Deprecated: In previous versions of postgres, the default was not to
inheritance hierarchy. Many of the commands that we get access to child classes. By experience this was found to be error
have already discussed -- <command>SELECT</command>, prone. Under the old syntax, to get the sub-classes you append "*"
<command>UPDATE</command> and <command>DELETE</command> -- to the table name. For example
support this <quote>ONLY</quote> notation.
</para> <programlisting>
<para> SELECT * from cities*;
Deprecated: In previous versions of postgres, the default was not to </programlisting>
get access to child classes. By experience this was found to be error
prone. Under the old syntax, to get the sub-classes you append "*" This old behaviour is still available by using a SET command:
to the table name. For example
<programlisting> <programlisting>
SELECT * from cities*; SET EXAMINE_SUBCLASS TO on;
</programlisting> </programlisting>
This old behaviour is still available by using a SET command... </para>
<programlisting>
SET EXAMINE_SUBCLASS TO on;
</programlisting>
</para>
</sect1> </sect1>
<sect1> <sect1>
......
doc/src/sgml/inherit.sgml
View file @ 0d2a78bf
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/inherit.sgml,v 1.8 2000/06/09 01:43:56 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/inherit.sgml,v 1.9 2000/06/14 13:12:52 thomas Exp $
--> -->
<chapter id="inherit"> <chapter id="inherit">
...@@ -40,6 +40,7 @@ CREATE TABLE capitals UNDER cities ( ...@@ -40,6 +40,7 @@ CREATE TABLE capitals UNDER cities (
The inheritance hierarchy is a actually a directed acyclic graph. The inheritance hierarchy is a actually a directed acyclic graph.
</para> </para>
</note> </note>
</para>
<para> <para>
For example, the following query finds the names of all cities, For example, the following query finds the names of all cities,
...@@ -87,6 +88,7 @@ CREATE TABLE capitals UNDER cities ( ...@@ -87,6 +88,7 @@ CREATE TABLE capitals UNDER cities (
</programlisting> </programlisting>
</para> </para>
<para>
Here the <quote>ONLY</quote> before cities indicates that the query should Here the <quote>ONLY</quote> before cities indicates that the query should
be run over only cities and not classes below cities in the be run over only cities and not classes below cities in the
inheritance hierarchy. Many of the commands that we inheritance hierarchy. Many of the commands that we
......
doc/src/sgml/release.sgml
View file @ 0d2a78bf
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.54 2000/06/05 10:57:57 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.55 2000/06/14 13:12:52 thomas Exp $
--> -->
<chapter id="release"> <chapter id="release">
<title>Release Notes</title> <title>Release Notes</title>
<sect1> <sect1>
<title>Release 7.0.2</title> <title>Release 7.0.2</title>
<!-- <!--
<docinfo> <docinfo>
<authorgroup> <authorgroup>
<author> <author>
<firstname>Bruce</firstname> <firstname>Bruce</firstname>
<surname>Momjian</surname> <surname>Momjian</surname>
</author> </author>
</authorgroup> </authorgroup>
<date>2000-06-05</date> <date>2000-06-05</date>
</docinfo> </docinfo>
--> -->
<para> <para>
2000-06-05 Release date 2000-06-05. This is a repackaging of 7.0.1 with added documentation.
</para> </para>
<para>
This is a repackaging of 7.0.1 with added documentation.
</para>
<sect2> <sect2>
<title>Migration to v7.0.2</title> <title>Migration to v7.0.2</title>
<para> <para>
A dump/restore is <emphasis>not</emphasis> required for those running A dump/restore is <emphasis>not</emphasis> required for those running
7.*. v7.*.
</para> </para>
</sect2> </sect2>
<sect2>
<title>Changes</title>
<para> <sect2>
<programlisting> <title>Changes</title>
<para>
<programlisting>
Added documentation to tarball. Added documentation to tarball.
</programlisting> </programlisting>
</para> </para>
</sect2> </sect2>
</sect1> </sect1>
<sect1> <sect1>
<title>Release 7.0.1</title> <title>Release 7.0.1</title>
<!-- <!--
<docinfo> <docinfo>
<authorgroup> <authorgroup>
<author> <author>
<firstname>Bruce</firstname> <firstname>Bruce</firstname>
<surname>Momjian</surname> <surname>Momjian</surname>
</author> </author>
</authorgroup> </authorgroup>
<date>2000-06-01</date> <date>2000-06-01</date>
</docinfo> </docinfo>
--> -->
<para> <para>
2000-06-01 Release date 2000-06-01.
</para> This is a cleanup release for 7.0.
<para> </para>
This is basically a cleanup release for 7.0.
</para>
<sect2>
<title>Migration to v7.0.1</title>
<sect2> <para>
<title>Migration to v7.0.1</title> A dump/restore is <emphasis>not</emphasis> required for those running
v7.0.
</para>
</sect2>
<para> <sect2>
A dump/restore is <emphasis>not</emphasis> required for those running <title>Changes</title>
7.0.
</para>
</sect2>
<sect2>
<title>Changes</title>
<para> <para>
<programlisting> <programlisting>
Fix many CLUSTER failures (Tom) Fix many CLUSTER failures (Tom)
Allow ALTER TABLE RENAME works on indexes (Tom) Allow ALTER TABLE RENAME works on indexes (Tom)
Fix plpgsql to handle datetime->timestamp and timespan->interval (Bruce) Fix plpgsql to handle datetime->timestamp and timespan->interval (Bruce)
...@@ -106,11 +102,10 @@ Fix too long syslog message (Tatsuo) ...@@ -106,11 +102,10 @@ Fix too long syslog message (Tatsuo)
Fix problem with quoted indexes that are too long (Tom) Fix problem with quoted indexes that are too long (Tom)
JDBC ResultSet.getTimestamp() fix (Gregory Krasnow & Floyd Marinescu) JDBC ResultSet.getTimestamp() fix (Gregory Krasnow & Floyd Marinescu)
ecpg changes (Michael) ecpg changes (Michael)
</programlisting> </programlisting>
</para> </para>
</sect2> </sect2>
</sect1> </sect1>
<sect1> <sect1>
<title>Release 7.0</title> <title>Release 7.0</title>
...@@ -126,9 +121,7 @@ ecpg changes (Michael) ...@@ -126,9 +121,7 @@ ecpg changes (Michael)
</docinfo> </docinfo>
--> -->
<para> <para>
2000-05-08 Released 2000-05-08.
</para>
<para>
This release contains improvements in many areas, demonstrating This release contains improvements in many areas, demonstrating
the continued growth of <productname>PostgreSQL</productname>. the continued growth of <productname>PostgreSQL</productname>.
There are more improvements and fixes in 7.0 than in any previous There are more improvements and fixes in 7.0 than in any previous
...@@ -287,6 +280,8 @@ Ack! This isn't yet in the code?? - thomas 2000-04-30 ...@@ -287,6 +280,8 @@ Ack! This isn't yet in the code?? - thomas 2000-04-30
</sect2> </sect2>
<sect2> <sect2>
<title>Changes</title>
<para> <para>
<programlisting> <programlisting>
Bug Fixes Bug Fixes
...@@ -611,87 +606,84 @@ New multibyte encodings ...@@ -611,87 +606,84 @@ New multibyte encodings
</sect2> </sect2>
</sect1> </sect1>
<sect1> <sect1>
<title>Release 6.5.3</title> <title>Release 6.5.3</title>
<!-- <!--
<docinfo> <docinfo>
<authorgroup> <authorgroup>
<author> <author>
<firstname>Bruce</firstname> <firstname>Bruce</firstname>
<surname>Momjian</surname> <surname>Momjian</surname>
</author> </author>
</authorgroup> </authorgroup>
<date>1999-10-13</date> <date>1999-10-13</date>
</docinfo> </docinfo>
--> -->
<para> <para>
1999-10-13 Released 1999-10-13.
</para> This is basically a cleanup release for 6.5.2. We have added a new
<para> pgaccess that was missing in 6.5.2, and installed an NT-specific fix.
This is basically a cleanup release for 6.5.2. We have added a new </para>
pgaccess that was missing in 6.5.2, and installed an NT-specific fix.
</para>
<sect2> <sect2>
<title>Migration to v6.5.3</title> <title>Migration to v6.5.3</title>
<para> <para>
A dump/restore is <emphasis>not</emphasis> required for those running A dump/restore is <emphasis>not</emphasis> required for those running
6.5.*. 6.5.*.
</para> </para>
</sect2> </sect2>
<sect2> <sect2>
<title>Changes</title> <title>Changes</title>
<para> <para>
<programlisting> <programlisting>
Updated version of pgaccess 0.98 Updated version of pgaccess 0.98
NT-specific patch NT-specific patch
Fix dumping rules on inherited tables Fix dumping rules on inherited tables
</programlisting> </programlisting>
</para> </para>
</sect2> </sect2>
</sect1> </sect1>
<sect1> <sect1>
<title>Release 6.5.2</title> <title>Release 6.5.2</title>
<!-- <!--
<docinfo> <docinfo>
<authorgroup> <authorgroup>
<author> <author>
<firstname>Bruce</firstname> <firstname>Bruce</firstname>
<surname>Momjian</surname> <surname>Momjian</surname>
</author> </author>
</authorgroup> </authorgroup>
<date>1999-09-15</date> <date>1999-09-15</date>
</docinfo> </docinfo>
--> -->
<para> <para>
1999-09-15 Released 1999-09-15.
</para> This is basically a cleanup release for 6.5.1. We have fixed a variety of
<para> problems reported by 6.5.1 users.
This is basically a cleanup release for 6.5.1. We have fixed a variety of </para>
problems reported by 6.5.1 users.
</para>
<sect2> <sect2>
<title>Migration to v6.5.2</title> <title>Migration to v6.5.2</title>
<para> <para>
A dump/restore is <emphasis>not</emphasis> required for those running A dump/restore is <emphasis>not</emphasis> required for those running
6.5.*. 6.5.*.
</para> </para>
</sect2> </sect2>
<sect2>
<title>Changes</title>
<para> <sect2>
<programlisting> <title>Changes</title>
<para>
<programlisting>
subselect+CASE fixes(Tom) subselect+CASE fixes(Tom)
Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren Sefcik) Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren Sefcik)
Fixes for CASE in WHERE join clauses(Tom) Fixes for CASE in WHERE join clauses(Tom)
...@@ -716,48 +708,47 @@ Repair logic error in LIKE: should not return LIKE_ABORT ...@@ -716,48 +708,47 @@ Repair logic error in LIKE: should not return LIKE_ABORT
when reach end of pattern before end of text(Tom) when reach end of pattern before end of text(Tom)
Repair incorrect cleanup of heap memory allocation during transaction abort(Tom) Repair incorrect cleanup of heap memory allocation during transaction abort(Tom)
Updated version of pgaccess 0.98 Updated version of pgaccess 0.98
</programlisting> </programlisting>
</para> </para>
</sect2> </sect2>
</sect1> </sect1>
<sect1> <sect1>
<title>Release 6.5.1</title> <title>Release 6.5.1</title>
<!-- <!--
<docinfo> <docinfo>
<authorgroup> <authorgroup>
<author> <author>
<firstname>Bruce</firstname> <firstname>Bruce</firstname>
<surname>Momjian</surname> <surname>Momjian</surname>
</author> </author>
</authorgroup> </authorgroup>
<date>1999-07-15</date> <date>1999-07-15</date>
</docinfo> </docinfo>
--> -->
<para> <para>
1999-07-15 Released 1999-07-15.
</para> </para>
<para> <para>
This is basically a cleanup release for 6.5. We have fixed a variety of This is basically a cleanup release for 6.5. We have fixed a variety of
problems reported by 6.5 users. problems reported by 6.5 users.
</para> </para>
<sect2>
<title>Migration to v6.5.1</title>
<sect2> <para>
<title>Migration to v6.5.1</title> A dump/restore is <emphasis>not</emphasis> required for those running
6.5.
</para>
</sect2>
<para> <sect2>
A dump/restore is <emphasis>not</emphasis> required for those running <title>Changes</title>
6.5.
</para>
</sect2>
<sect2>
<title>Changes</title>
<para> <para>
<programlisting> <programlisting>
Add NT README file Add NT README file
Portability fixes for linux_ppc, Irix, linux_alpha, OpenBSD, alpha Portability fixes for linux_ppc, Irix, linux_alpha, OpenBSD, alpha
Remove QUERY_LIMIT, use SELECT...LIMIT Remove QUERY_LIMIT, use SELECT...LIMIT
...@@ -781,30 +772,27 @@ Shared library dependencies fixed (Tom) ...@@ -781,30 +772,27 @@ Shared library dependencies fixed (Tom)
Fixed glitches affecting GROUP BY in subselects(Tom) Fixed glitches affecting GROUP BY in subselects(Tom)
Fix some compiler warnings (Tomoaki Nishiyama) Fix some compiler warnings (Tomoaki Nishiyama)
Add Win1250 (Czech) support (Pavel Behal) Add Win1250 (Czech) support (Pavel Behal)
</programlisting> </programlisting>
</para> </para>
</sect2> </sect2>
</sect1> </sect1>
<sect1> <sect1>
<title>Release 6.5</title> <title>Release 6.5</title>
<!-- <!--
<docinfo> <docinfo>
<authorgroup> <authorgroup>
<author> <author>
<firstname>Bruce</firstname> <firstname>Bruce</firstname>
<surname>Momjian</surname> <surname>Momjian</surname>
</author> </author>
</authorgroup> </authorgroup>
<date>1999-06-09</date> <date>1999-06-09</date>
</docinfo> </docinfo>
--> -->
<para> <para>
1999-06-09 Released 1999-06-09.
</para>
<para>
This release marks a major step in the development team's mastery of the source This release marks a major step in the development team's mastery of the source
code we inherited from Berkeley. You will see we are now easily adding code we inherited from Berkeley. You will see we are now easily adding
major features, thanks to the increasing size and experience of our major features, thanks to the increasing size and experience of our
...@@ -1023,6 +1011,8 @@ Add Win1250 (Czech) support (Pavel Behal) ...@@ -1023,6 +1011,8 @@ Add Win1250 (Czech) support (Pavel Behal)
</sect2> </sect2>
<sect2> <sect2>
<title>Changes</title>
<para> <para>
<programlisting> <programlisting>
Bug Fixes Bug Fixes
...@@ -1412,10 +1402,12 @@ is required for those wishing to migrate data from any ...@@ -1412,10 +1402,12 @@ is required for those wishing to migrate data from any
previous release of <productname>Postgres</productname>. previous release of <productname>Postgres</productname>.
</para> </para>
</sect2> </sect2>
<sect2>
<para> <sect2>
<programlisting> <title>Changes</title>
<para>
<programlisting>
Bug Fixes Bug Fixes
--------- ---------
Fix for a tiny memory leak in PQsetdb/PQfinish(Bryan) Fix for a tiny memory leak in PQsetdb/PQfinish(Bryan)
...@@ -1664,12 +1656,11 @@ For upgrades from pre-v6.3 installations, ...@@ -1664,12 +1656,11 @@ For upgrades from pre-v6.3 installations,
refer to the installation and migration instructions for v6.3. refer to the installation and migration instructions for v6.3.
</para> </para>
<sect2> <sect2>
<title>Changes</title>
<para> <para>
<programlisting> <programlisting>
Changes
-------
Configure detection improvements for tcl/tk(Brook Milligan, Alvin) Configure detection improvements for tcl/tk(Brook Milligan, Alvin)
Manual page improvements(Bruce) Manual page improvements(Bruce)
BETWEEN and LIKE fix(Thomas) BETWEEN and LIKE fix(Thomas)
...@@ -1688,29 +1679,28 @@ libreadline cleanup(Erwan MAS) ...@@ -1688,29 +1679,28 @@ libreadline cleanup(Erwan MAS)
Remove DISTDIR(Bruce) Remove DISTDIR(Bruce)
Makefile dependency cleanup(Jeroen van Vianen) Makefile dependency cleanup(Jeroen van Vianen)
ASSERT fixes(Bruce) ASSERT fixes(Bruce)
</programlisting> </programlisting>
</para> </para>
</sect2> </sect2>
</sect1> </sect1>
<sect1>
<title>Release 6.3.1</title>
<!--
<docinfo>
<authorgroup>
<author>
<firstname>Bruce</firstname>
<surname>Momjian</surname>
</author>
</authorgroup>
<date>1998-03-23</date>
</docinfo>
-->
<para> <sect1>
1998-03-23 <title>Release 6.3.1</title>
</para> <!--
<para> <docinfo>
Summary: <authorgroup>
<author>
<firstname>Bruce</firstname>
<surname>Momjian</surname>
</author>
</authorgroup>
<date>1998-03-23</date>
</docinfo>
-->
<para>
Released 1998-03-23.
Summary:
<itemizedlist> <itemizedlist>
<listitem> <listitem>
...@@ -1750,12 +1740,11 @@ For upgrades from pre-v6.3 installations, ...@@ -1750,12 +1740,11 @@ For upgrades from pre-v6.3 installations,
refer to the installation and migration instructions for v6.3. refer to the installation and migration instructions for v6.3.
</para> </para>
<sect2> <sect2>
<title>Changes</title>
<para> <para>
<programlisting> <programlisting>
Changes
-------
ecpg cleanup/fixes, now version 1.1(Michael Meskes) ecpg cleanup/fixes, now version 1.1(Michael Meskes)
pg_user cleanup(Bruce) pg_user cleanup(Bruce)
large object fix for pg_dump and tclsh (alvin) large object fix for pg_dump and tclsh (alvin)
...@@ -1783,59 +1772,58 @@ Fix Alpha port(Dwayne Bailey) ...@@ -1783,59 +1772,58 @@ Fix Alpha port(Dwayne Bailey)
Fix for text arrays containing quotes(Doug Gibson) Fix for text arrays containing quotes(Doug Gibson)
Solaris compile fix(Albert Chin-A-Young) Solaris compile fix(Albert Chin-A-Young)
Better identify tcl and tk libs and includes(Bruce) Better identify tcl and tk libs and includes(Bruce)
</programlisting> </programlisting>
</para> </para>
</sect2> </sect2>
</sect1> </sect1>
<sect1>
<title>Release 6.3</title>
<!--
<docinfo>
<authorgroup>
<author>
<firstname>Bruce</firstname>
<surname>Momjian</surname>
</author>
</authorgroup>
<date>1998-03-01</date>
</docinfo>
-->
<para> <sect1>
1998-03-01 <title>Release 6.3</title>
</para> <!--
<para> <docinfo>
There are <emphasis>many</emphasis> new features and improvements in this release. <authorgroup>
Here is a brief, incomplete summary: <author>
<firstname>Bruce</firstname>
<surname>Momjian</surname>
</author>
</authorgroup>
<date>1998-03-01</date>
</docinfo>
-->
<itemizedlist> <para>
<listitem> Released 1998-03-01.
<para> There are <emphasis>many</emphasis> new features and improvements in this release.
Many new SQL features, including Here is a brief, incomplete summary:
full <acronym>SQL92</acronym> subselect capability
(everything is here but target-list subselects).
</para>
</listitem>
<listitem> <itemizedlist>
<para> <listitem>
Support for client-side environment variables to specify time zone and date style. <para>
</para> Many new SQL features, including
</listitem> full <acronym>SQL92</acronym> subselect capability
(everything is here but target-list subselects).
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Socket interface for client/server connection. This is the default now Support for client-side environment variables to specify time zone and date style.
so you may need to start <application>postmaster</application> with the </para>
<option>-i</option> flag. </listitem>
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Better password authorization mechanisms. Default table permissions have changed. Socket interface for client/server connection. This is the default now
</para> so you may need to start <application>postmaster</application> with the
</listitem> <option>-i</option> flag.
</para>
</listitem>
<listitem>
<para>
Better password authorization mechanisms. Default table permissions have changed.
</para>
</listitem>
<listitem> <listitem>
<para> <para>
...@@ -1843,101 +1831,101 @@ Better password authorization mechanisms. Default table permissions have changed ...@@ -1843,101 +1831,101 @@ Better password authorization mechanisms. Default table permissions have changed
has been removed. Performance has been improved. has been removed. Performance has been improved.
</para> </para>
</listitem> </listitem>
</itemizedlist>
</para>
</itemizedlist> <note>
</para> <para>
Bruce Momjian wrote the following notes to introduce the new release.
<note> </para>
<para> </note>
Bruce Momjian wrote the following notes to introduce the new release.
</para>
</note>
<para> <para>
There are some general 6.3 issues that I want to mention. These are There are some general 6.3 issues that I want to mention. These are
only the big items that can not be described in one sentence. A review only the big items that can not be described in one sentence. A review
of the detailed changes list is still needed. of the detailed changes list is still needed.
</para> </para>
<para> <para>
First, we now have subselects. Now that we have them, I would like to First, we now have subselects. Now that we have them, I would like to
mention that without subselects, SQL is a very limited language. mention that without subselects, SQL is a very limited language.
Subselects are a major feature, and you should review your code for Subselects are a major feature, and you should review your code for
places where subselects provide a better solution for your queries. I places where subselects provide a better solution for your queries. I
think you will find that there are more uses for subselects than you may think you will find that there are more uses for subselects than you may
think. Vadim has put us on the big SQL map with subselects, and fully think. Vadim has put us on the big SQL map with subselects, and fully
functional ones too. The only thing you can't do with subselects is to functional ones too. The only thing you can't do with subselects is to
use them in the target list. use them in the target list.
</para> </para>
<para> <para>
Second, 6.3 uses unix domain sockets rather than TCP/IP by default. To Second, 6.3 uses unix domain sockets rather than TCP/IP by default. To
enable connections from other machines, you have to use the new enable connections from other machines, you have to use the new
postmaster -i option, and of course edit pg_hba.conf. Also, for this postmaster -i option, and of course edit pg_hba.conf. Also, for this
reason, the format of pg_hba.conf has changed. reason, the format of pg_hba.conf has changed.
</para> </para>
<para> <para>
Third, char() fields will now allow faster access than varchar() or Third, char() fields will now allow faster access than varchar() or
text. Specifically, the text and varchar() have a penalty for access to text. Specifically, the text and varchar() have a penalty for access to
any columns after the first column of this type. char() used to also any columns after the first column of this type. char() used to also
have this access penalty, but it no longer does. This may suggest that have this access penalty, but it no longer does. This may suggest that
you redesign some of your tables, especially if you have short character you redesign some of your tables, especially if you have short character
columns that you have defined as varchar() or text. This and other columns that you have defined as varchar() or text. This and other
changes make 6.3 even faster than earlier releases. changes make 6.3 even faster than earlier releases.
</para> </para>
<para> <para>
We now have passwords definable independent of any Unix file. There are We now have passwords definable independent of any Unix file. There are
new SQL USER commands. See the pg_hba.conf manual page for more new SQL USER commands. See the pg_hba.conf manual page for more
information. There is a new table, pg_shadow, which is used to store information. There is a new table, pg_shadow, which is used to store
user information and user passwords, and it by default only SELECT-able user information and user passwords, and it by default only SELECT-able
by the postgres super-user. pg_user is now a view of pg_shadow, and is by the postgres super-user. pg_user is now a view of pg_shadow, and is
SELECT-able by PUBLIC. You should keep using pg_user in your SELECT-able by PUBLIC. You should keep using pg_user in your
application without changes. application without changes.
</para> </para>
<para> <para>
User-created tables now no longer have SELECT permission to PUBLIC by User-created tables now no longer have SELECT permission to PUBLIC by
default. This was done because the ANSI standard requires it. You can default. This was done because the ANSI standard requires it. You can
of course GRANT any permissions you want after the table is created. of course GRANT any permissions you want after the table is created.
System tables continue to be SELECT-able by PUBLIC. System tables continue to be SELECT-able by PUBLIC.
</para> </para>
<para> <para>
We also have real deadlock detection code. No more sixty-second We also have real deadlock detection code. No more sixty-second
timeouts. And the new locking code implements a FIFO better, so there timeouts. And the new locking code implements a FIFO better, so there
should be less resource starvation during heavy use. should be less resource starvation during heavy use.
</para> </para>
<para> <para>
Many complaints have been made about inadequate documenation in previous Many complaints have been made about inadequate documenation in previous
releases. Thomas has put much effort into many new manuals for this releases. Thomas has put much effort into many new manuals for this
release. Check out the doc/ directory. release. Check out the doc/ directory.
</para> </para>
<para> <para>
For performance reasons, time travel is gone, but can be implemented For performance reasons, time travel is gone, but can be implemented
using triggers (see pgsql/contrib/spi/README). Please check out the new using triggers (see pgsql/contrib/spi/README). Please check out the new
\d command for types, operators, etc. Also, views have their own \d command for types, operators, etc. Also, views have their own
permissions now, not based on the underlying tables, so permissions on permissions now, not based on the underlying tables, so permissions on
them have to be set separately. Check /pgsql/interfaces for some new them have to be set separately. Check /pgsql/interfaces for some new
ways to talk to <productname>Postgres</productname>. ways to talk to <productname>Postgres</productname>.
</para> </para>
<para> <para>
This is the first release that really required an explanation for This is the first release that really required an explanation for
existing users. In many ways, this was necessary because the new existing users. In many ways, this was necessary because the new
release removes many limitations, and the work-arounds people were using release removes many limitations, and the work-arounds people were using
are no longer needed. are no longer needed.
</para> </para>
<sect2> <sect2>
<title>Migration to v6.3</title> <title>Migration to v6.3</title>
<para> <para>
A dump/restore using <application>pg_dump</application> A dump/restore using <application>pg_dump</application>
or <application>pg_dumpall</application> or <application>pg_dumpall</application>
is required for those wishing to migrate data from any is required for those wishing to migrate data from any
previous release of <productname>Postgres</productname>. previous release of <productname>Postgres</productname>.
</para> </para>
</sect2> </sect2>
<sect2> <sect2>
<title>Changes</title>
<para> <para>
<programlisting> <programlisting>
Bug Fixes Bug Fixes
--------- ---------
Fix binary cursors broken by MOVE implementation(Vadim) Fix binary cursors broken by MOVE implementation(Vadim)
...@@ -2176,12 +2164,12 @@ from psql to update the existing system table: ...@@ -2176,12 +2164,12 @@ from psql to update the existing system table:
This will need to be done to every existing database, including template1. This will need to be done to every existing database, including template1.
</para> </para>
</sect2> </sect2>
<sect2>
<para> <sect2>
<programlisting> <title>Changes</title>
Changes
------- <para>
<programlisting>
Allow TIME and TYPE column names(Thomas) Allow TIME and TYPE column names(Thomas)
Allow larger range of true/false as boolean values(Thomas) Allow larger range of true/false as boolean values(Thomas)
Support output of "now" and "current"(Thomas) Support output of "now" and "current"(Thomas)
...@@ -2193,10 +2181,10 @@ Fix avg(cash) computation(Thomas) ...@@ -2193,10 +2181,10 @@ Fix avg(cash) computation(Thomas)
Fix for specifying a column twice in ORDER/GROUP BY(Vadim) Fix for specifying a column twice in ORDER/GROUP BY(Vadim)
Documented new libpq function to return affected rows, PQcmdTuples(Bruce) Documented new libpq function to return affected rows, PQcmdTuples(Bruce)
Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan) Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan)
</programlisting> </programlisting>
</para> </para>
</sect2> </sect2>
</sect1> </sect1>
<sect1> <sect1>
<title>Release 6.2</title> <title>Release 6.2</title>
...@@ -2243,10 +2231,11 @@ because the COPY output format was improved from the 1.02 release. ...@@ -2243,10 +2231,11 @@ because the COPY output format was improved from the 1.02 release.
</para> </para>
</sect2> </sect2>
<sect2> <sect2>
<title>Changes</title>
<para> <para>
<programlisting> <programlisting>
Bug Fixes Bug Fixes
--------- ---------
Fix problems with pg_dump for inheritance, sequences, archive tables(Bruce) Fix problems with pg_dump for inheritance, sequences, archive tables(Bruce)
...@@ -2388,12 +2377,11 @@ Refer to the release notes for v6.1 for more details. ...@@ -2388,12 +2377,11 @@ Refer to the release notes for v6.1 for more details.
</para> </para>
</sect2> </sect2>
<sect2> <sect2>
<title>Changes</title>
<para> <para>
<programlisting> <programlisting>
Changes
-------
fix for SET with options (Thomas) fix for SET with options (Thomas)
allow pg_dump/pg_dumpall to preserve ownership of all tables/objects(Bruce) allow pg_dump/pg_dumpall to preserve ownership of all tables/objects(Bruce)
new psql \connect option allows changing usernames without changing databases new psql \connect option allows changing usernames without changing databases
...@@ -2411,10 +2399,10 @@ major fix for endian handling of communication to server(Thomas, Tatsuo) ...@@ -2411,10 +2399,10 @@ major fix for endian handling of communication to server(Thomas, Tatsuo)
Fix for Solaris assembler and include files(Yoshihiko Ichikawa) Fix for Solaris assembler and include files(Yoshihiko Ichikawa)
allow underscores in usernames(Bruce) allow underscores in usernames(Bruce)
pg_dumpall now returns proper status, portability fix(Bruce) pg_dumpall now returns proper status, portability fix(Bruce)
</programlisting> </programlisting>
</para> </para>
</sect2> </sect2>
</sect1> </sect1>
<sect1> <sect1>
<title>Release 6.1</title> <title>Release 6.1</title>
...@@ -2492,10 +2480,11 @@ because the COPY output format was improved from the 1.02 release. ...@@ -2492,10 +2480,11 @@ because the COPY output format was improved from the 1.02 release.
</para> </para>
</sect2> </sect2>
<sect2> <sect2>
<title>Changes</title>
<para> <para>
<programlisting> <programlisting>
Bug Fixes Bug Fixes
--------- ---------
packet length checking in library routines packet length checking in library routines
...@@ -2635,10 +2624,11 @@ because the COPY output format was improved from the 1.02 release. ...@@ -2635,10 +2624,11 @@ because the COPY output format was improved from the 1.02 release.
</para> </para>
</sect2> </sect2>
<sect2> <sect2>
<title>Changes</title>
<para> <para>
<programlisting> <programlisting>
Bug Fixes Bug Fixes
--------- ---------
ALTER TABLE bug - running postgress process needs to re-read table definition ALTER TABLE bug - running postgress process needs to re-read table definition
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment