From 0d2a78bf23a96a6de837f05c6c3f40f146b8635d Mon Sep 17 00:00:00 2001 From: "Thomas G. Lockhart" Date: Wed, 14 Jun 2000 13:12:52 +0000 Subject: [PATCH] Repair markup to allow clean doc builds. --- doc/src/sgml/advanced.sgml | 85 ++-- doc/src/sgml/inherit.sgml | 4 +- doc/src/sgml/release.sgml | 780 ++++++++++++++++++------------------- 3 files changed, 433 insertions(+), 436 deletions(-) diff --git a/doc/src/sgml/advanced.sgml b/doc/src/sgml/advanced.sgml index a76e4cc780..2807c8bc86 100644 --- a/doc/src/sgml/advanced.sgml +++ b/doc/src/sgml/advanced.sgml @@ -1,5 +1,5 @@ @@ -59,21 +59,22 @@ CREATE TABLE capitals ( The inheritance hierarchy is a directed acyclic graph. + - - For example, the following query finds the names of all cities, - including state capitals, that are located at an altitude - over 500ft, the query is: + + For example, the following query finds the names of all cities, + including state capitals, that are located at an altitude + over 500ft, the query is: - - SELECT c.name, c.altitude + +SELECT c.name, c.altitude FROM cities c WHERE c.altitude > 500; - + - which returns: + which returns: - + +----------+----------+ |name | altitude | +----------+----------+ @@ -83,16 +84,16 @@ CREATE TABLE capitals ( +----------+----------+ |Madison | 845 | +----------+----------+ - - + + - - On the other hand, the following query finds - all the cities, but not capital cities - that are situated at an attitude of 500ft or higher: + + On the other hand, the following query finds + all the cities, but not capital cities + that are situated at an attitude of 500ft or higher: - - SELECT name, altitude + +SELECT name, altitude FROM ONLY cities WHERE altitude > 500; @@ -103,30 +104,34 @@ CREATE TABLE capitals ( +----------+----------+ |Mariposa | 1953 | +----------+----------+ - - + + + + Here the ONLY 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 -- SELECT, + UPDATE and DELETE -- + support this ONLY notation. + - Here the ONLY 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 -- SELECT, - UPDATE and DELETE -- - support this ONLY notation. - - - Deprecated: In previous versions of postgres, the default was not to - 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 "*" - to the table name. For example - - SELECT * from cities*; - - This old behaviour is still available by using a SET command... - - SET EXAMINE_SUBCLASS TO on; - - + + Deprecated: In previous versions of postgres, the default was not to + 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 "*" + to the table name. For example + + +SELECT * from cities*; + + + This old behaviour is still available by using a SET command: + + +SET EXAMINE_SUBCLASS TO on; + + diff --git a/doc/src/sgml/inherit.sgml b/doc/src/sgml/inherit.sgml index 0fa3f79be3..73a2678655 100644 --- a/doc/src/sgml/inherit.sgml +++ b/doc/src/sgml/inherit.sgml @@ -1,5 +1,5 @@ @@ -40,6 +40,7 @@ CREATE TABLE capitals UNDER cities ( The inheritance hierarchy is a actually a directed acyclic graph. + For example, the following query finds the names of all cities, @@ -87,6 +88,7 @@ CREATE TABLE capitals UNDER cities ( + Here the ONLY 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 diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 7d8f613a90..11e98f12d6 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,87 +1,83 @@ Release Notes - -Release 7.0.2 - + + Release 7.0.2 + - -2000-06-05 - - -This is a repackaging of 7.0.1 with added documentation. - + + Release date 2000-06-05. This is a repackaging of 7.0.1 with added documentation. + - -Migration to v7.0.2 + + Migration to v7.0.2 - -A dump/restore is not required for those running -7.*. - - - -Changes + + A dump/restore is not required for those running + v7.*. + + - - + + Changes + + + Added documentation to tarball. - - - - + + + + - -Release 7.0.1 - + + Release 7.0.1 + - -2000-06-01 - - -This is basically a cleanup release for 7.0. - + + Release date 2000-06-01. + This is a cleanup release for 7.0. + + + Migration to v7.0.1 - -Migration to v7.0.1 + + A dump/restore is not required for those running + v7.0. + + - -A dump/restore is not required for those running -7.0. - - - -Changes + + Changes - - + + Fix many CLUSTER failures (Tom) Allow ALTER TABLE RENAME works on indexes (Tom) Fix plpgsql to handle datetime->timestamp and timespan->interval (Bruce) @@ -106,11 +102,10 @@ Fix too long syslog message (Tatsuo) Fix problem with quoted indexes that are too long (Tom) JDBC ResultSet.getTimestamp() fix (Gregory Krasnow & Floyd Marinescu) ecpg changes (Michael) - - - - - + + + + Release 7.0 @@ -126,9 +121,7 @@ ecpg changes (Michael) --> -2000-05-08 - - + Released 2000-05-08. This release contains improvements in many areas, demonstrating the continued growth of PostgreSQL. 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 + Changes + Bug Fixes @@ -611,87 +606,84 @@ New multibyte encodings - -Release 6.5.3 - + + Release 6.5.3 + - -1999-10-13 - - -This is basically a cleanup release for 6.5.2. We have added a new -pgaccess that was missing in 6.5.2, and installed an NT-specific fix. - + + Released 1999-10-13. + This is basically a cleanup release for 6.5.2. We have added a new + pgaccess that was missing in 6.5.2, and installed an NT-specific fix. + - -Migration to v6.5.3 + + Migration to v6.5.3 - -A dump/restore is not required for those running -6.5.*. - - - -Changes + + A dump/restore is not required for those running + 6.5.*. + + + + Changes - - + + Updated version of pgaccess 0.98 NT-specific patch Fix dumping rules on inherited tables - - - - + + + + - -Release 6.5.2 - + + Release 6.5.2 + - -1999-09-15 - - -This is basically a cleanup release for 6.5.1. We have fixed a variety of -problems reported by 6.5.1 users. - + + Released 1999-09-15. + This is basically a cleanup release for 6.5.1. We have fixed a variety of + problems reported by 6.5.1 users. + - -Migration to v6.5.2 + + Migration to v6.5.2 - -A dump/restore is not required for those running -6.5.*. - - - -Changes + + A dump/restore is not required for those running + 6.5.*. + + - - + + Changes + + + subselect+CASE fixes(Tom) Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren Sefcik) Fixes for CASE in WHERE join clauses(Tom) @@ -716,48 +708,47 @@ Repair logic error in LIKE: should not return LIKE_ABORT when reach end of pattern before end of text(Tom) Repair incorrect cleanup of heap memory allocation during transaction abort(Tom) Updated version of pgaccess 0.98 - - - - + + + + + + Release 6.5.1 + - -Release 6.5.1 - + + Released 1999-07-15. + + + This is basically a cleanup release for 6.5. We have fixed a variety of + problems reported by 6.5 users. + - -1999-07-15 - - -This is basically a cleanup release for 6.5. We have fixed a variety of -problems reported by 6.5 users. - + + Migration to v6.5.1 + + A dump/restore is not required for those running + 6.5. + + - -Migration to v6.5.1 + + Changes - -A dump/restore is not required for those running -6.5. - - - -Changes - - - + + Add NT README file Portability fixes for linux_ppc, Irix, linux_alpha, OpenBSD, alpha Remove QUERY_LIMIT, use SELECT...LIMIT @@ -781,30 +772,27 @@ Shared library dependencies fixed (Tom) Fixed glitches affecting GROUP BY in subselects(Tom) Fix some compiler warnings (Tomoaki Nishiyama) Add Win1250 (Czech) support (Pavel Behal) - - - - + + + + - - -Release 6.5 - + + Release 6.5 + -1999-06-09 - - + Released 1999-06-09. 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 major features, thanks to the increasing size and experience of our @@ -1023,6 +1011,8 @@ Add Win1250 (Czech) support (Pavel Behal) + Changes + Bug Fixes @@ -1412,10 +1402,12 @@ is required for those wishing to migrate data from any previous release of Postgres. - - - + +Changes + + + Bug Fixes --------- Fix for a tiny memory leak in PQsetdb/PQfinish(Bryan) @@ -1664,12 +1656,11 @@ For upgrades from pre-v6.3 installations, refer to the installation and migration instructions for v6.3. - + + Changes - - -Changes -------- + + Configure detection improvements for tcl/tk(Brook Milligan, Alvin) Manual page improvements(Bruce) BETWEEN and LIKE fix(Thomas) @@ -1688,29 +1679,28 @@ libreadline cleanup(Erwan MAS) Remove DISTDIR(Bruce) Makefile dependency cleanup(Jeroen van Vianen) ASSERT fixes(Bruce) - - - - - -Release 6.3.1 - + + + + - -1998-03-23 - - -Summary: + + Release 6.3.1 + + + + Released 1998-03-23. + Summary: @@ -1750,12 +1740,11 @@ For upgrades from pre-v6.3 installations, refer to the installation and migration instructions for v6.3. - + + Changes - - -Changes -------- + + ecpg cleanup/fixes, now version 1.1(Michael Meskes) pg_user cleanup(Bruce) large object fix for pg_dump and tclsh (alvin) @@ -1783,59 +1772,58 @@ Fix Alpha port(Dwayne Bailey) Fix for text arrays containing quotes(Doug Gibson) Solaris compile fix(Albert Chin-A-Young) Better identify tcl and tk libs and includes(Bruce) - - - - - -Release 6.3 - + + + + - -1998-03-01 - - -There are many new features and improvements in this release. -Here is a brief, incomplete summary: + + Release 6.3 + - - - -Many new SQL features, including -full SQL92 subselect capability -(everything is here but target-list subselects). - - + + Released 1998-03-01. + There are many new features and improvements in this release. + Here is a brief, incomplete summary: - - -Support for client-side environment variables to specify time zone and date style. - - + + + + Many new SQL features, including + full SQL92 subselect capability + (everything is here but target-list subselects). + + - - -Socket interface for client/server connection. This is the default now -so you may need to start postmaster with the - flag. - - + + + Support for client-side environment variables to specify time zone and date style. + + - - -Better password authorization mechanisms. Default table permissions have changed. - - + + + Socket interface for client/server connection. This is the default now + so you may need to start postmaster with the + flag. + + + + + + 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. + + - - + + + Bruce Momjian wrote the following notes to introduce the new release. + + - - -Bruce Momjian wrote the following notes to introduce the new release. - - + + 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 + of the detailed changes list is still needed. + + + First, we now have subselects. Now that we have them, I would like to + mention that without subselects, SQL is a very limited language. + Subselects are a major feature, and you should review your code for + 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. 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 + use them in the target list. + + + 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 + postmaster -i option, and of course edit pg_hba.conf. Also, for this + reason, the format of pg_hba.conf has changed. + + + Third, char() fields will now allow faster access than varchar() or + 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 + 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 + columns that you have defined as varchar() or text. This and other + changes make 6.3 even faster than earlier releases. + + + 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 + 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 + 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 + application without changes. + + + User-created tables now no longer have SELECT permission to PUBLIC by + default. This was done because the ANSI standard requires it. You can + of course GRANT any permissions you want after the table is created. + System tables continue to be SELECT-able by PUBLIC. + + + We also have real deadlock detection code. No more sixty-second + timeouts. And the new locking code implements a FIFO better, so there + should be less resource starvation during heavy use. + + + Many complaints have been made about inadequate documenation in previous + releases. Thomas has put much effort into many new manuals for this + release. Check out the doc/ directory. + + + For performance reasons, time travel is gone, but can be implemented + using triggers (see pgsql/contrib/spi/README). Please check out the new + \d command for types, operators, etc. Also, views have their own + permissions now, not based on the underlying tables, so permissions on + them have to be set separately. Check /pgsql/interfaces for some new + ways to talk to Postgres. + + + This is the first release that really required an explanation for + existing users. In many ways, this was necessary because the new + release removes many limitations, and the work-arounds people were using + are no longer needed. + - -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 -of the detailed changes list is still needed. - - -First, we now have subselects. Now that we have them, I would like to -mention that without subselects, SQL is a very limited language. -Subselects are a major feature, and you should review your code for -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. 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 -use them in the target list. - - -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 -postmaster -i option, and of course edit pg_hba.conf. Also, for this -reason, the format of pg_hba.conf has changed. - - -Third, char() fields will now allow faster access than varchar() or -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 -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 -columns that you have defined as varchar() or text. This and other -changes make 6.3 even faster than earlier releases. - - -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 -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 -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 -application without changes. - - -User-created tables now no longer have SELECT permission to PUBLIC by -default. This was done because the ANSI standard requires it. You can -of course GRANT any permissions you want after the table is created. -System tables continue to be SELECT-able by PUBLIC. - - -We also have real deadlock detection code. No more sixty-second -timeouts. And the new locking code implements a FIFO better, so there -should be less resource starvation during heavy use. - - -Many complaints have been made about inadequate documenation in previous -releases. Thomas has put much effort into many new manuals for this -release. Check out the doc/ directory. - - -For performance reasons, time travel is gone, but can be implemented -using triggers (see pgsql/contrib/spi/README). Please check out the new -\d command for types, operators, etc. Also, views have their own -permissions now, not based on the underlying tables, so permissions on -them have to be set separately. Check /pgsql/interfaces for some new -ways to talk to Postgres. - - -This is the first release that really required an explanation for -existing users. In many ways, this was necessary because the new -release removes many limitations, and the work-arounds people were using -are no longer needed. - + + Migration to v6.3 - -Migration to v6.3 + + A dump/restore using pg_dump + or pg_dumpall + is required for those wishing to migrate data from any + previous release of Postgres. + + - -A dump/restore using pg_dump -or pg_dumpall -is required for those wishing to migrate data from any -previous release of Postgres. - - + + Changes - - - - + + Bug Fixes --------- Fix binary cursors broken by MOVE implementation(Vadim) @@ -2176,12 +2164,12 @@ from psql to update the existing system table: This will need to be done to every existing database, including template1. - - - -Changes -------- + + Changes + + + Allow TIME and TYPE column names(Thomas) Allow larger range of true/false as boolean values(Thomas) Support output of "now" and "current"(Thomas) @@ -2193,10 +2181,10 @@ Fix avg(cash) computation(Thomas) Fix for specifying a column twice in ORDER/GROUP BY(Vadim) Documented new libpq function to return affected rows, PQcmdTuples(Bruce) Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan) - - - - + + + + Release 6.2 @@ -2243,10 +2231,11 @@ because the COPY output format was improved from the 1.02 release. - + + Changes - - + + Bug Fixes --------- 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. - + + Changes - - -Changes -------- + + fix for SET with options (Thomas) allow pg_dump/pg_dumpall to preserve ownership of all tables/objects(Bruce) 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) Fix for Solaris assembler and include files(Yoshihiko Ichikawa) allow underscores in usernames(Bruce) pg_dumpall now returns proper status, portability fix(Bruce) - - - - + + + + Release 6.1 @@ -2492,10 +2480,11 @@ because the COPY output format was improved from the 1.02 release. - + + Changes - - + + Bug Fixes --------- packet length checking in library routines @@ -2635,10 +2624,11 @@ because the COPY output format was improved from the 1.02 release. - + + Changes - - + + Bug Fixes --------- ALTER TABLE bug - running postgress process needs to re-read table definition