Index: doc/src/sgml/array.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/array.sgml,v retrieving revision 1.48 diff -c -c -r1.48 array.sgml *** doc/src/sgml/array.sgml 19 Nov 2005 01:50:08 -0000 1.48 --- doc/src/sgml/array.sgml 20 Mar 2006 18:40:41 -0000 *************** *** 559,566 **** embedded in element values will be backslash-escaped. For numeric data types it is safe to assume that double quotes will never appear, but for textual data types one should be prepared to cope with either presence ! or absence of quotes. (This is a change in behavior from pre-7.2 ! PostgreSQL releases.) --- 559,565 ---- embedded in element values will be backslash-escaped. For numeric data types it is safe to assume that double quotes will never appear, but for textual data types one should be prepared to cope with either presence ! or absence of quotes. Index: doc/src/sgml/backup.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v retrieving revision 2.79 diff -c -c -r2.79 backup.sgml *** doc/src/sgml/backup.sgml 10 Mar 2006 19:10:46 -0000 2.79 --- doc/src/sgml/backup.sgml 20 Mar 2006 18:40:42 -0000 *************** *** 1211,1218 **** the number after the first dot changes). This does not apply to different minor releases under the same major release (where the number after the second dot changes); these always have compatible ! storage formats. For example, releases 7.0.1, 7.1.2, and 7.2 are ! not compatible, whereas 7.1.1 and 7.1.2 are. When you update between compatible versions, you can simply replace the executables and reuse the data directory on disk. Otherwise you need to back up your data and restore it on the new server. This has to be done --- 1211,1218 ---- the number after the first dot changes). This does not apply to different minor releases under the same major release (where the number after the second dot changes); these always have compatible ! storage formats. For example, releases 7.2.1, 7.3.2, and 7.4 are ! not compatible, whereas 7.2.1 and 7.2.2 are. When you update between compatible versions, you can simply replace the executables and reuse the data directory on disk. Otherwise you need to back up your data and restore it on the new server. This has to be done Index: doc/src/sgml/config.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/config.sgml,v retrieving revision 1.52 diff -c -c -r1.52 config.sgml *** doc/src/sgml/config.sgml 10 Mar 2006 19:10:47 -0000 1.52 --- doc/src/sgml/config.sgml 20 Mar 2006 18:40:44 -0000 *************** *** 3789,3801 **** This controls the inheritance semantics, in particular whether ! subtables are included by various commands by default. They were ! not included in versions prior to 7.1. If you need the old ! behavior you can set this variable to off, but in ! the long run you are encouraged to change your applications to ! use the ONLY key word to exclude subtables. ! See for more information about ! inheritance. --- 3789,3796 ---- This controls the inheritance semantics, in particular whether ! subtables are included by various commands by default. This was ! added for compatibility with releases prior to 7.1. Index: doc/src/sgml/datatype.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v retrieving revision 1.166 diff -c -c -r1.166 datatype.sgml *** doc/src/sgml/datatype.sgml 10 Mar 2006 19:10:47 -0000 1.166 --- doc/src/sgml/datatype.sgml 20 Mar 2006 18:40:46 -0000 *************** *** 894,915 **** string. ! ! If one explicitly casts a value to character ! varying(n) or ! character(n), then an over-length ! value will be truncated to n characters without ! raising an error. (This too is required by the ! SQL standard.) ! ! ! ! ! Prior to PostgreSQL 7.2, strings that were too long were ! always truncated without raising an error, in either explicit or ! implicit casting contexts. ! ! The notations varchar(n) and --- 894,907 ---- string. ! ! If one explicitly casts a value to character ! varying(n) or ! character(n), then an over-length ! value will be truncated to n characters without ! raising an error. (This too is required by the ! SQL standard.) ! The notations varchar(n) and *************** *** 2899,2913 **** - - - Prior to PostgreSQL 7.2, bit data - was always silently truncated or zero-padded on the right, with - or without an explicit cast. This was changed to comply with the - SQL standard. - - - Refer to for information about the syntax --- 2891,2896 ---- Index: doc/src/sgml/datetime.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v retrieving revision 2.48 diff -c -c -r2.48 datetime.sgml *** doc/src/sgml/datetime.sgml 10 Mar 2006 19:10:47 -0000 2.48 --- doc/src/sgml/datetime.sgml 20 Mar 2006 18:40:47 -0000 *************** *** 171,180 **** Gregorian years AD 1-99 may be entered by using 4 digits with leading ! zeros (e.g., 0099 is AD 99). Previous versions of ! PostgreSQL accepted years with three ! digits and with single digits, but as of version 7.0 the rules have ! been tightened up to reduce the possibility of ambiguity. --- 171,177 ---- Gregorian years AD 1-99 may be entered by using 4 digits with leading ! zeros (e.g., 0099 is AD 99). Index: doc/src/sgml/ddl.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/ddl.sgml,v retrieving revision 1.55 diff -c -c -r1.55 ddl.sgml *** doc/src/sgml/ddl.sgml 18 Feb 2006 23:14:45 -0000 1.55 --- doc/src/sgml/ddl.sgml 20 Mar 2006 18:40:52 -0000 *************** *** 2145,2165 **** Deprecated ! In previous versions of PostgreSQL, the default behavior was not to include child tables in queries. This was ! found to be error prone and is also in violation of the SQL ! standard. Under the old syntax, to include the child tables you append ! * to the table name. For example: ! ! SELECT * from cities*; ! ! You can still explicitly specify scanning child tables by ! appending *, as well as explicitly specify not ! scanning child tables by writing ONLY. But ! beginning in version 7.1, the default behavior for an undecorated ! table name is to scan its child tables too, whereas before the ! default was not to do so. To get the old default behavior, ! disable the configuration option. --- 2145,2155 ---- Deprecated ! In releases of PostgreSQL prior to 7.1, the default behavior was not to include child tables in queries. This was ! found to be error prone and also in violation of the SQL ! standard. You can get the pre-7.1 behavior by turning off the ! configuration option. Index: doc/src/sgml/func.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/func.sgml,v retrieving revision 1.313 diff -c -c -r1.313 func.sgml *** doc/src/sgml/func.sgml 10 Mar 2006 20:15:25 -0000 1.313 --- doc/src/sgml/func.sgml 20 Mar 2006 18:41:01 -0000 *************** *** 6118,6131 **** the result is given to the full available precision. - - - Prior to PostgreSQL 7.2, the precision - parameters were unimplemented, and the result was always given - in integer seconds. - - - Some examples: --- 6118,6123 ---- Index: doc/src/sgml/libpq.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v retrieving revision 1.206 diff -c -c -r1.206 libpq.sgml *** doc/src/sgml/libpq.sgml 10 Mar 2006 19:10:48 -0000 1.206 --- doc/src/sgml/libpq.sgml 20 Mar 2006 18:41:05 -0000 *************** *** 689,699 **** functions described below to get at the contents of PGconn. Avoid directly referencing the fields of the PGconn structure because they are subject to change in the future. - (Beginning in PostgreSQL release 6.4, the - definition of the struct behind PGconn is not even provided in libpq-fe.h. - If you have old code that accesses PGconn fields directly, you can keep using it - by including libpq-int.h too, but you are encouraged to fix the code - soon.) --- 689,694 ---- *************** *** 2972,2978 **** typedef struct pgNotify { char *relname; /* notification condition name */ ! int be_pid; /* process ID of server process */ char *extra; /* notification parameter */ } PGnotify; --- 2967,2973 ---- typedef struct pgNotify { char *relname; /* notification condition name */ ! int be_pid; /* process ID of notifying server process */ char *extra; /* notification parameter */ } PGnotify; *************** *** 2986,2999 **** always point to an empty string.) - - - In PostgreSQL 6.4 and later, - the be_pid is that of the notifying server process, - whereas in earlier versions it was always the PID of your own server process. - - - gives a sample program that illustrates the use of asynchronous notification. --- 2981,2986 ---- *************** *** 4288,4303 **** - - libpq-int.h - If your codes references the header file - libpq-int.h and you refuse to fix your code to - not use it, starting in PostgreSQL 7.2, this file will be found in - includedir/postgresql/internal/libpq-int.h, - so you need to add the appropriate option to - your compiler command line. - - --- 4275,4280 ---- Index: doc/src/sgml/lobj.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v retrieving revision 1.39 diff -c -c -r1.39 lobj.sgml *** doc/src/sgml/lobj.sgml 10 Mar 2006 19:10:48 -0000 1.39 --- doc/src/sgml/lobj.sgml 20 Mar 2006 18:41:05 -0000 *************** *** 25,67 **** values. This is not described here. ! ! History ! ! POSTGRES 4.2, the indirect predecessor ! of PostgreSQL, supported three standard ! implementations of large objects: as files external to the ! POSTGRES server, as external files ! managed by the POSTGRES server, and as ! data stored within the POSTGRES ! database. This caused considerable confusion among users. As a ! result, only support for large objects as data stored within the ! database is retained in PostgreSQL. ! Even though this is slower to access, it provides stricter data ! integrity. For historical reasons, this storage scheme is ! referred to as Inversion large ! objects. (You will see the term Inversion used ! occasionally to mean the same thing as large object.) Since ! PostgreSQL 7.1, all large objects are ! placed in one system table called ! pg_largeobject. ! ! ! TOAST ! versus large objects ! ! PostgreSQL 7.1 introduced a mechanism ! (nicknamed TOAST) that allows ! data values to be much larger than single pages. This ! makes the large object facility partially obsolete. One remaining advantage of the large object facility is that it allows values up to 2 GB in size, whereas TOASTed fields can be at ! most 1 GB. Also, large objects can be manipulated piece-by-piece much more ! easily than ordinary data fields, so the practical limits are considerably ! different. --- 25,50 ---- values. This is not described here. ! ! Introduction ! ! TOAST ! versus large objects ! ! All large objects are placed in a single system table called ! pg_largeobject. ! PostgreSQL also supports a storage system called ! TOAST that automatically stores values ! larger than a single database page into a secondary storage area per table. ! This makes the large object facility partially obsolete. One remaining advantage of the large object facility is that it allows values up to 2 GB in size, whereas TOASTed fields can be at ! most 1 GB. Also, large objects can be randomly modified using a read/write ! API that is more efficient than performing such operations using ! TOAST. *************** *** 70,77 **** Implementation Features ! The large object implementation breaks large ! objects up into chunks and stores the chunks in rows in the database. A B-tree index guarantees fast searches for the correct chunk number when doing random access reads and writes. --- 53,60 ---- Implementation Features ! The large object implementation breaks large ! objects up into chunks and stores the chunks in rows in the database. A B-tree index guarantees fast searches for the correct chunk number when doing random access reads and writes. *************** *** 86,95 **** PostgreSQL client interface libraries provide for accessing large objects. All large object manipulation using these functions must take ! place within an SQL transaction block. (This requirement is ! strictly enforced as of PostgreSQL 6.5, though it ! has been an implicit requirement in previous versions, resulting ! in misbehavior if ignored.) The PostgreSQL large object interface is modeled after the Unix file-system interface, with analogues of open, read, --- 69,75 ---- PostgreSQL client interface libraries provide for accessing large objects. All large object manipulation using these functions must take ! place within an SQL transaction block. The PostgreSQL large object interface is modeled after the Unix file-system interface, with analogues of open, read, Index: doc/src/sgml/maintenance.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v retrieving revision 1.54 diff -c -c -r1.54 maintenance.sgml *** doc/src/sgml/maintenance.sgml 10 Mar 2006 19:10:48 -0000 1.54 --- doc/src/sgml/maintenance.sgml 20 Mar 2006 18:41:05 -0000 *************** *** 82,96 **** ! Beginning in PostgreSQL 7.2, the standard form ! of VACUUM can run in parallel with normal database operations ! (selects, inserts, updates, deletes, but not changes to table definitions). ! Routine vacuuming is therefore not nearly as intrusive as it was in prior ! releases, and it is not as critical to try to schedule it at low-usage ! times of day. ! ! ! Beginning in PostgreSQL 8.0, there are configuration parameters that can be adjusted to further reduce the performance impact of background vacuuming. See --- 82,90 ---- ! The standard form of VACUUM can run in parallel with ! normal database operations (SELECTs, INSERTs, UPDATEs, DELETEs, but not ! changes to table definitions). Beginning in PostgreSQL 8.0, there are configuration parameters that can be adjusted to further reduce the performance impact of background vacuuming. See *************** *** 245,256 **** It is possible to run ANALYZE on specific tables and even just specific columns of a table, so the flexibility exists to update some statistics more frequently than others if your application requires it. ! In practice, however, the usefulness of this feature is doubtful. ! Beginning in PostgreSQL 7.2, ! ANALYZE is a fairly fast operation even on large tables, ! because it uses a statistical random sampling of the rows of a table ! rather than reading every single row. So it's probably much simpler ! to just run it over the whole database every so often. --- 239,247 ---- It is possible to run ANALYZE on specific tables and even just specific columns of a table, so the flexibility exists to update some statistics more frequently than others if your application requires it. ! In practice, however, the usefulness of this feature is doubtful because ! ANALYZE is such a fast operation it is often best to just run ! it on the entire database. *************** *** 295,312 **** transactions that were in the past appear to be in the future — which means their outputs become invisible. In short, catastrophic data loss. (Actually the data is still there, but that's cold comfort if you can't ! get at it.) ! ! ! ! Prior to PostgreSQL 7.2, the only defense ! against XID wraparound was to re-initdb at least every 4 ! billion transactions. This of course was not very satisfactory for ! high-traffic sites, so a better solution has been devised. The new ! approach allows a server to remain up indefinitely, without ! initdb or any sort of restart. The price is this ! maintenance requirement: every table in the database must ! be vacuumed at least once every billion transactions. --- 286,293 ---- transactions that were in the past appear to be in the future — which means their outputs become invisible. In short, catastrophic data loss. (Actually the data is still there, but that's cold comfort if you can't ! get at it.) To avoid this, it is necessary to vacuum every table ! in every database at least once every billion transactions. Index: doc/src/sgml/mvcc.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/mvcc.sgml,v retrieving revision 2.55 diff -c -c -r2.55 mvcc.sgml *** doc/src/sgml/mvcc.sgml 10 Mar 2006 19:10:48 -0000 2.55 --- doc/src/sgml/mvcc.sgml 20 Mar 2006 18:41:06 -0000 *************** *** 899,908 **** TABLE locks the whole table.) This should be taken into account when porting applications to PostgreSQL from other environments. - (Before version 6.5 PostgreSQL used - read locks, and so this above consideration is also relevant when - upgrading from PostgreSQL versions - prior to 6.5.) --- 899,904 ---- Index: doc/src/sgml/rules.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/rules.sgml,v retrieving revision 1.44 diff -c -c -r1.44 rules.sgml *** doc/src/sgml/rules.sgml 22 Oct 2005 14:44:35 -0000 1.44 --- doc/src/sgml/rules.sgml 20 Mar 2006 18:41:06 -0000 *************** *** 2043,2052 **** Another situation is cases on UPDATE where it depends on the change of an attribute if an action should be performed or ! not. In PostgreSQL version 6.4, the ! attribute specification for rule events is disabled (it will have ! its comeback latest in 6.5, maybe earlier ! - stay tuned). So for now the only way to create a rule as in the shoelace_log example is to do it with a rule qualification. That results in an extra query that is performed always, even if the attribute of interest cannot --- 2043,2049 ---- Another situation is cases on UPDATE where it depends on the change of an attribute if an action should be performed or ! not. The only way to create a rule as in the shoelace_log example is to do it with a rule qualification. That results in an extra query that is performed always, even if the attribute of interest cannot Index: doc/src/sgml/storage.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/storage.sgml,v retrieving revision 1.9 diff -c -c -r1.9 storage.sgml *** doc/src/sgml/storage.sgml 10 Mar 2006 19:10:49 -0000 1.9 --- doc/src/sgml/storage.sgml 20 Mar 2006 18:41:07 -0000 *************** *** 188,201 **** Since PostgreSQL uses a fixed page size (commonly ! 8Kb), and does not allow tuples to span multiple pages, it's not possible to ! store very large field values directly. Before PostgreSQL 7.1 ! there was a hard limit of just under one page on the total amount of data that ! could be put into a table row. In release 7.1 and later, this limit is ! overcome by allowing large field values to be compressed and/or broken up into ! multiple physical rows. This happens transparently to the user, with only ! small impact on most of the backend code. The technique is affectionately ! known as TOAST (or the best thing since sliced bread). --- 188,199 ---- Since PostgreSQL uses a fixed page size (commonly ! 8Kb), and does not allow tuples to span multiple pages, so it's not possible to ! store very large field values directly. To overcome this limitation, large ! field values are compressed and/or broken up into multiple physical rows. ! This happens transparently to the user, with only small impact on most of the ! backend code. The technique is affectionately known as TOAST ! (or the best thing since sliced bread). Index: doc/src/sgml/xfunc.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/xfunc.sgml,v retrieving revision 1.111 diff -c -c -r1.111 xfunc.sgml *** doc/src/sgml/xfunc.sgml 10 Mar 2006 19:10:49 -0000 1.111 --- doc/src/sgml/xfunc.sgml 20 Mar 2006 18:41:08 -0000 *************** *** 1192,1206 **** command pg_config --pkglibdir. - - Before PostgreSQL release 7.2, only - exact absolute paths to object files could be specified in - CREATE FUNCTION. This approach is now deprecated - since it makes the function definition unnecessarily unportable. - It's best to specify just the shared library name with no path nor - extension, and let the search mechanism provide that information - instead. - --- 1192,1197 ---- *************** *** 1915,1929 **** --includedir-serverpg_configwith user-defined C functions to find out where the PostgreSQL server header files are installed on your system (or the system that your ! users will be running on). This option is new with ! PostgreSQL 7.2. For ! PostgreSQL 7.1 you should use the option ! . (pg_config ! will exit with a non-zero status if it encounters an unknown ! option.) For releases prior to 7.1 you will have to guess, ! but since that was before the current calling conventions were ! introduced, it is unlikely that you want to support those ! releases. --- 1906,1912 ---- --includedir-serverpg_configwith user-defined C functions to find out where the PostgreSQL server header files are installed on your system (or the system that your ! users will be running on).