With us supporting only PG >=8.0, I think we can remove some mentions of
pre-7.4 releases. The attached patch show my proposed removals.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
+ If your life is a hard drive, Christ can be your backup. +
Index: doc/src/sgml/datatype.sgml
===
RCS file: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v
retrieving revision 1.242
diff -c -c -r1.242 datatype.sgml
*** doc/src/sgml/datatype.sgml 17 Feb 2010 04:19:37 - 1.242
--- doc/src/sgml/datatype.sgml 23 Feb 2010 00:16:14 -
***
*** 715,725
! Prior to PostgreSQL 7.4, the precision in
! float(p) was taken to mean
! so many decimal digits. This has been corrected to match the SQL
! standard, which specifies that the precision is measured in binary
! digits. The assumption that real and
double precision have exactly 24 and 53 bits in the
mantissa respectively is correct for IEEE-standard floating point
implementations. On non-IEEE platforms it might be off a little, but
--- 715,721
! The assumption that real and
double precision have exactly 24 and 53 bits in the
mantissa respectively is correct for IEEE-standard floating point
implementations. On non-IEEE platforms it might be off a little, but
***
*** 795,805
! Prior to PostgreSQL 7.3, serial
! implied UNIQUE. This is no longer automatic. If
! you wish a serial column to have a unique constraint or be a
! primary key, it must now be specified, just like
! any other data type.
--- 791,799
! If you wish a serial column to have a unique constraint or be
! a primary key, it must be specified, just like any other data
! type.
***
*** 1521,1534
-
-
- Prior to PostgreSQL 7.3, writing just
- timestamp was equivalent to timestamp with
- time zone. This was changed for SQL compliance.
-
-
-
time, timestamp, and
interval accept an optional precision value
--- 1515,1520
Index: doc/src/sgml/ddl.sgml
===
RCS file: /cvsroot/pgsql/doc/src/sgml/ddl.sgml,v
retrieving revision 1.88
diff -c -c -r1.88 ddl.sgml
*** doc/src/sgml/ddl.sgml 23 Oct 2009 05:24:52 - 1.88
--- doc/src/sgml/ddl.sgml 23 Feb 2010 00:16:14 -
***
*** 1795,1812
! In PostgreSQL versions before 7.3,
! table names beginning with pg_ were reserved. This is
! no longer true: you can create such a table name if you wish, in
! any non-system schema. However, it's best to continue to avoid
! such names, to ensure that you won't suffer a conflict if some
! future version defines a system table named the same as your
! table. (With the default search path, an unqualified reference to
! your table name would then be resolved as the system table instead.)
! System tables will continue to follow the convention of having
! names beginning with pg_, so that they will not
! conflict with unqualified user-table names so long as users avoid
! the pg_ prefix.
--- 1795,1806
! It is best to avoid table names beginning with pg_
! because they might someday conflict with system catalogs of the
! same name. (PostgreSQL system catalog
! table names always start with pg_). Of course, table
! names can always be schema-qualified to avoid conflicting with
! system catalog table names.
***
*** 3040,3054
-
-
- Foreign key constraint dependencies and serial column dependencies
- from PostgreSQL versions prior to 7.3
- are not maintained or created during the
- upgrade process. All other dependency types will be properly
- created during an upgrade from a pre-7.3 database.
-
-
--- 3034,3039
Index: doc/src/sgml/libpq.sgml
===
RCS file: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v
retrieving revision 1.300
diff -c -c -r1.300 libpq.sgml
*** doc/src/sgml/libpq.sgml 17 Feb 2010 04:19:37 - 1.300
--- doc/src/sgml/libpq.sgml 23 Feb 2010 00:16:14 -
***
*** 1203,1216
has been sent to the server and not yet completed.
-
-
- PQtransactionStatus will give incorrect results when using
- a PostgreSQL 7.3 server that has the parameter autocommit
- set to off. The server-side autocommit feature has been
- deprecated and does not exist in l
