Index: doc/src/sgml/errcodes.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/errcodes.sgml,v retrieving revision 1.7 diff -c -r1.7 errcodes.sgml *** doc/src/sgml/errcodes.sgml 31 Jul 2004 23:04:54 -0000 1.7 --- doc/src/sgml/errcodes.sgml 21 Aug 2004 12:49:31 -0000 *************** *** 1133,1139 **** Class 58 ! System Error (errors external to PostgreSQL itself) --- 1133,1139 ---- Class 58 ! System Error (errors external to PostgreSQL itself) Index: doc/src/sgml/problems.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/problems.sgml,v retrieving revision 2.18 diff -c -r2.18 problems.sgml *** doc/src/sgml/problems.sgml 9 Mar 2004 16:57:46 -0000 2.18 --- doc/src/sgml/problems.sgml 21 Aug 2004 12:47:10 -0000 *************** *** 11,18 **** PostgreSQL more reliable because even the utmost care cannot guarantee that every part of PostgreSQL ! will work on every ! platform under every circumstance. --- 11,17 ---- PostgreSQL more reliable because even the utmost care cannot guarantee that every part of PostgreSQL ! will work on every platform under every circumstance. *************** *** 241,249 **** in each new release, so it is quite possible that a bug you have encountered in an older release of PostgreSQL has already been fixed. We can only provide limited support for ! sites using older releases of PostgreSQL; if you require more ! than we can provide, consider acquiring a commercial support ! contract. --- 240,248 ---- in each new release, so it is quite possible that a bug you have encountered in an older release of PostgreSQL has already been fixed. We can only provide limited support for ! sites using older releases of PostgreSQL; if you ! require more than we can provide, consider acquiring a ! commercial support contract. Index: doc/src/sgml/release.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/release.sgml,v retrieving revision 1.287 diff -c -r1.287 release.sgml *** doc/src/sgml/release.sgml 21 Aug 2004 03:25:34 -0000 1.287 --- doc/src/sgml/release.sgml 22 Aug 2004 19:03:39 -0000 *************** *** 27,103 **** ! This is the first PostgreSQL release to natively run on Microsoft ! Windows as a server. It can run as a Windows service. This release ! supports NT-based Windows releases like Win2000, XP, Win2003. ! Older releases like Windows 95, 98, and ME are not supported because ! these operating systems do not have the infrastructure to ! support PostgreSQL. A separate installer project has been created ! to ease installation on Windows: ! http://pgfoundry.org/projects/pginstaller. Previous releases required the Unix emulation toolkit Cygwin for ! Win32 server support. PostgreSQL has always supported clients on Win32. ! Savepoints Improve Transaction Control Savepoints allow specific parts of a transaction to be aborted without affecting the remainder of the transaction. Prior ! releases had no such capability; there was no way to recover from ! a statement failure within a transaction except by aborting the whole ! transaction. This feature is valuable ! for application writers who require error recovery within a ! complex transaction. ! Point-In-Time Recovery Increases Reliability ! Though PostgreSQL is very reliable, in previous releases there ! was no way to recover from disk drive failure except to restore ! from a previous backup or use a standby replication server. ! Point-in-time recovery allows continuous backup of the server. ! You can recover either to the point of failure or to some ! transaction in the past. ! Tablespaces Simplify Disk Layout ! Tablespaces allow administrators ! to select the file systems used for storage of databases, ! schemas, tables, or indexes. This improves performance and ! control over disk space usage. Prior releases used ! initlocation and manual symlink management for such tasks. ! Improved Buffer Management, CHECKPOINT, VACUUM --- 27,106 ---- ! This is the first PostgreSQL ! release to natively run on Microsoft Windows as a server. It ! can run as a Windows service. This release supports NT-based ! Windows releases like Win2000, XP, Win2003. Older releases ! like Windows 95, 98, and ME are not supported because these ! operating systems do not have the infrastructure to support ! PostgreSQL. A separate installer ! project has been created to ease installation on Windows: ! http://pgfoundry.org/projects/pginstaller. Previous releases required the Unix emulation toolkit Cygwin for ! Win32 server support. PostgreSQL ! has always supported clients on Win32. ! Savepoints Savepoints allow specific parts of a transaction to be aborted without affecting the remainder of the transaction. Prior ! releases had no such capability; there was no way to recover ! from a statement failure within a transaction except by ! aborting the whole transaction. This feature is valuable for ! application writers who require error recovery within a ! complex transaction. ! Point-In-Time Recovery ! Though PostgreSQL is very reliable, ! in previous releases there was no way to recover from disk ! drive failure except to restore from a previous backup or use ! a standby replication server. Point-in-time recovery allows ! continuous backup of the server. You can recover either to ! the point of failure or to some transaction in the past. ! Tablespaces ! Tablespaces allow administrators to select the file systems ! used for storage of databases, schemas, tables, or ! indexes. This improves performance and control over disk space ! usage. Prior releases used initlocation and ! manual symlink management for such tasks. ! Improved Buffer Management, CHECKPOINT, ! VACUUM *************** *** 117,123 **** ! A column's data type can now be changed with ALTER TABLE. --- 120,127 ---- ! A column's data type can now be changed with ALTER ! TABLE. *************** *** 130,151 **** A new version of the plperl server-side language now ! supports a persistent shared storage area, triggers, returning records ! and arrays of records, and SPI calls to access the database. ! COPY Handles Comma-Separated-Value Files ! COPY can now read and write comma-separated-value (CSV) files. It ! has the flexibility to interpret non-standard quoting and ! separation characters too. --- 134,155 ---- A new version of the plperl server-side language now ! supports a persistent shared storage area, triggers, returning records ! and arrays of records, and SPI calls to access the database. ! CSV support in COPY ! COPY can now read and write ! comma-separated-value (CSV) files. It has the flexibility to ! interpret non-standard quoting and separation characters too. *************** *** 181,189 **** Server configuration parameters SortMem and ! VacuumMem have been renamed to work_mem and ! maintenance_work_mem to better reflect their use. The ! original names are still supported in SET and SHOW. --- 185,194 ---- Server configuration parameters SortMem and ! VacuumMem have been renamed to work_mem ! and maintenance_work_mem to better reflect their ! use. The original names are still supported in ! SET and SHOW. *************** *** 246,253 **** ! The server now warns of empty strings passed to oid/float4/float8 ! data types. In the next major release, doing this will generate an error. --- 251,259 ---- ! The server now warns of empty strings passed to ! oid/float4/float8 data ! types. In the next major release, doing this will generate an error. *************** *** 292,299 **** ! EXECUTE now returns a completion tag that matches the executed ! statement. --- 298,305 ---- ! EXECUTE now returns a completion tag that ! matches the executed statement. *************** *** 307,314 **** ! Now that tablespaces have been implemented, initlocation has been ! removed. --- 313,320 ---- ! Now that tablespaces have been implemented, ! initlocation has been removed. *************** *** 321,338 **** ignored as well as leading whitespace (which has always been ignored). - - - - The 8.1 release will remove the function to_char(interval) - . - - Changes --- 327,372 ---- ignored as well as leading whitespace (which has always been ignored). + Deprecated Features + + + Some aspects of PostgreSQL's behavior + have been determined to be suboptimal. For the sake of backward + compatibility these have not been removed in 8.0, but they are + considered deprecated and will be removed in the next major + release. + + + + + + The 8.1 release will remove the function + to_char(interval). + + + + + + By default, tables in PostgreSQL 8.0 + and earlier are created with OIDs. In the next release, this + will not be the case: to create a table + that contains OIDs, the WITH OIDS clause must + be specified or the default_use_oids + configuration parameter must be enabled. Users are encouraged to + explicitely use WITH OIDS if their tables + require OIDs for compatibility with future releases of + PostgreSQL. + + + + + + Changes *************** *** 396,405 **** Add ability to prolong vacuum to reduce performance impact (Jan) ! On busy systems, VACUUM performs many I/O requests which can hurt ! performance for other users. This release allows you to slow down ! VACUUM to reduce its impact on other users, though this increases the ! total duration of VACUUM. --- 430,440 ---- Add ability to prolong vacuum to reduce performance impact (Jan) ! On busy systems, VACUUM performs many I/O ! requests which can hurt performance for other users. This ! release allows you to slow down VACUUM to ! reduce its impact on other users, though this increases the ! total duration of VACUUM. *************** *** 469,475 **** ! Add type-specific ANALYZE statistics capability (Mark Cave-Ayland) This feature allows more flexibility in generating statistics --- 504,511 ---- ! Add type-specific ANALYZE statistics ! capability (Mark Cave-Ayland) This feature allows more flexibility in generating statistics *************** *** 479,485 **** ! Allow collection of ANALYZE statistics for expression indexes (Tom) Expression indexes (also called functional indexes) allow users to --- 515,522 ---- ! Allow collection of ANALYZE statistics for ! expression indexes (Tom) Expression indexes (also called functional indexes) allow users to *************** *** 493,499 **** ! New two-stage sampling method for ANALYZE (Manfred Koizar) This gives better statistics for asymmetric data distributions. --- 530,537 ---- ! New two-stage sampling method for ANALYZE ! (Manfred Koizar) This gives better statistics for asymmetric data distributions. *************** *** 502,512 **** ! Speed up TRUNCATE (Tom) This buys back some of the performance loss observed in 7.4, while still ! keeping TRUNCATE transaction-safe. --- 540,550 ---- ! Speed up TRUNCATE (Tom) This buys back some of the performance loss observed in 7.4, while still ! keeping TRUNCATE transaction-safe. *************** *** 671,693 **** ! Allow DECLARE CURSOR to take parameters (Oliver Jowett) ! It is now useful to issue DECLARE CURSOR in a Parse message with ! parameters. The parameter values sent at Bind time will be substituted ! into the execution of the cursor's query. ! Fix hash joins and aggregates of INET and CIDR data types (Tom) ! Release 7.4 handled hashing of mixed INET and CIDR values incorrectly. ! (This bug did not exist in prior releases because they wouldn't try ! to hash either datatype.) --- 709,735 ---- ! Allow DECLARE CURSOR to take parameters ! (Oliver Jowett) ! It is now useful to issue DECLARE CURSOR in a ! Parse message with parameters. The parameter values sent at ! Bind time will be substituted into the execution of the cursor's ! query. ! Fix hash joins and aggregates of inet and ! cidr data types (Tom) ! Release 7.4 handled hashing of mixed inet and ! cidr values incorrectly. (This bug did not exist ! in prior releases because they wouldn't try to hash either ! datatype.) *************** *** 719,726 **** ! Allow BEGIN WORK to specify transaction isolation levels like START ! TRANSACTION (Bruce) --- 761,769 ---- ! Allow BEGIN WORK to specify transaction ! isolation levels like START TRANSACTION does ! (Bruce) *************** *** 824,835 **** ! Change EXECUTE to return a completion tag matching the executed statement ! (Kris Jurka) ! Previous releases return an EXECUTE tag for any EXECUTE call. In ! this release, the tag returned will reflect the command executed. --- 867,879 ---- ! Change EXECUTE to return a completion tag ! matching the executed statement (Kris Jurka) ! Previous releases return an EXECUTE tag for ! any EXECUTE call. In this release, the tag ! returned will reflect the command executed. *************** *** 864,877 **** control whether tables are created with OIDs by default (Neil) ! This allows administrators to default all CREATE TABLE commands to ! create tables without OID columns. ! Add WITH / WITHOUT OIDS clause to CREATE TABLE AS (Neil) --- 908,922 ---- control whether tables are created with OIDs by default (Neil) ! This allows administrators to default all CREATE ! TABLE commands to create tables without OID columns. ! Add WITH / WITHOUT OIDS clause to CREATE TABLE ! AS (Neil) *************** *** 911,917 **** ! Allow multiple ALTER actions in a single ALTER TABLE command (Rod) This is particularly useful for ALTER commands that rewrite the --- 956,963 ---- ! Allow multiple ALTER actions in a single ALTER ! TABLE command (Rod) This is particularly useful for ALTER commands that rewrite the *************** *** 923,929 **** ! Allow ALTER TABLE to add SERIAL columns (Tom) This is related to the new capability of adding defaults for new --- 969,976 ---- ! Allow ALTER TABLE to add serial ! columns (Tom) This is related to the new capability of adding defaults for new *************** *** 996,1008 **** ! Allow CREATE SCHEMA to create triggers, indexes, and sequences (Neil) ! Add ALSO keyword to CREATE RULE (Fabien Coelho) This allows ALSO to be added to rule creation to contrast it with --- 1043,1057 ---- ! Allow CREATE SCHEMA to create triggers, ! indexes, and sequences (Neil) ! Add ALSO keyword to CREATE RULE (Fabien ! Coelho) This allows ALSO to be added to rule creation to contrast it with *************** *** 1012,1034 **** ! Add NOWAIT option to LOCK command (Tatsuo) ! This allows the LOCK command to fail if it would have to wait for ! the requested lock. ! Allow COPY to read and write comma-separated-value (CSV) files (Andrew, Bruce) ! Generate error if the COPY delimiter and NULL string conflict (Bruce) --- 1061,1085 ---- ! Add NOWAIT option to LOCK (Tatsuo) ! This allows the LOCK command to fail if it ! would have to wait for the requested lock. ! Allow COPY to read and write ! comma-separated-value (CSV) files (Andrew, Bruce) ! Generate error if the COPY delimiter and NULL ! string conflict (Bruce) *************** *** 1040,1046 **** ! Avoid locking conflict between CREATE INDEX and CHECKPOINT (Tom) In 7.3 and 7.4, a long-running btree index build could block concurrent --- 1091,1098 ---- ! Avoid locking conflict between CREATE INDEX ! and CHECKPOINT (Tom) In 7.3 and 7.4, a long-running btree index build could block concurrent *************** *** 1051,1064 **** ! Database-wide ANALYZE does not hold locks across tables (Tom) ! This reduces the potential for deadlocks against other backends that ! want exclusive locks on tables. To get the benefit of this change, ! do not execute database-wide ANALYZE inside a transaction block ! (BEGIN block); it must be able to commit and start a new transaction ! for each table. --- 1103,1118 ---- ! Database-wide ANALYZE does not hold locks ! across tables (Tom) ! This reduces the potential for deadlocks against other backends ! that want exclusive locks on tables. To get the benefit of this ! change, do not execute database-wide ANALYZE ! inside a transaction block (BEGIN block); it ! must be able to commit and start a new transaction for each ! table. *************** *** 1067,1077 **** Erase MD5 user passwords when a user is renamed (Bruce) ! PostgreSQL uses the user name as salt when encrypting passwords ! via MD5. When a user name is changed, their salt no longer matches ! the stored MD5 password, so the stored password becomes useless. ! In this release a notice is generated and the password ! is cleared. A new password must then be assigned. --- 1121,1132 ---- Erase MD5 user passwords when a user is renamed (Bruce) ! PostgreSQL uses the user name as salt ! when encrypting passwords via MD5. When a user name is changed, ! their salt no longer matches the stored MD5 password, so the ! stored password becomes useless. In this release a notice is ! generated and the password is cleared. A new password must then ! be assigned. *************** *** 1127,1133 **** Reject non-rectangular array literals as erroneous (Joe) ! Formerly, array_in would silently build a surprising result. --- 1182,1189 ---- Reject non-rectangular array literals as erroneous (Joe) ! Formerly, array_in would silently build a ! surprising result. *************** *** 1174,1184 **** ! Change factorial function to return NUMERIC (Gavin) ! Returning NUMERIC allows the factorial function to work for a wider ! range of input values. --- 1230,1240 ---- ! Change factorial function to return numeric (Gavin) ! Returning numeric allows the factorial function to ! work for a wider range of input values. *************** *** 1217,1223 **** ! Better support for IEEE Infinity and NaN values in float4, float8 (Neil) These should now work on all platforms that support IEEE-compliant --- 1273,1280 ---- ! Better support for IEEE Infinity and NaN values in ! float4, float8 (Neil) These should now work on all platforms that support IEEE-compliant *************** *** 1448,1454 **** ! Make psql \copy match COPY command syntax fully (Tom) --- 1505,1512 ---- ! Make psql \copy match COPY command syntax ! fully (Tom) *************** *** 1460,1466 **** ! Add CLUSTER information to psql \d display (Bruce) --- 1518,1525 ---- ! Add CLUSTER information to psql \d display ! (Bruce) *************** *** 1478,1484 **** ! Add global psql config file, psqlrc.sample (Bruce) This allows a central file where global psql startup commands can --- 1537,1544 ---- ! Add global psql config file, psqlrc.sample ! (Bruce) This allows a central file where global psql startup commands can *************** *** 1594,1601 **** ! Allow PQoidValue(), PQcmdTuples(), and PQoidStatus() to work ! on EXECUTE commands (Neil) --- 1654,1661 ---- ! Allow PQoidValue(), PQcmdTuples(), and PQoidStatus() to work on ! EXECUTE commands (Neil) *************** *** 1665,1674 **** New "PostgreSQL" CVS tag (Marc) ! This was done to make it easier for organizations to manage their own ! copies of the PostgreSQL CVS repository. File version stamps from the ! master repository will not get munged by checking into or out of ! a copied repository. --- 1725,1735 ---- New "PostgreSQL" CVS tag (Marc) ! This was done to make it easier for organizations to manage ! their own copies of the PostgreSQL ! CVS repository. File version stamps from the master repository ! will not get munged by checking into or out of a copied ! repository. *************** *** 1880,1886 **** ! New /contrib/trgm, trigram matching for PostgreSQL (Teodor) --- 1941,1948 ---- ! New /contrib/trgm, trigram matching for ! PostgreSQL (Teodor) *************** *** 2037,2043 **** This fixes a difficult-to-exploit security hole. ! Avoid locking conflict between ANALYZE and LISTEN/NOTIFY Numerous translation updates (various contributors) --- 2099,2105 ---- This fixes a difficult-to-exploit security hole. ! Avoid locking conflict between ANALYZE and LISTEN/NOTIFY Numerous translation updates (various contributors) Index: doc/src/sgml/runtime.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/runtime.sgml,v retrieving revision 1.278 diff -c -r1.278 runtime.sgml *** doc/src/sgml/runtime.sgml 16 Aug 2004 02:12:29 -0000 1.278 --- doc/src/sgml/runtime.sgml 22 Aug 2004 05:26:00 -0000 *************** *** 1206,1222 **** Specifies the delay between activity rounds for the ! background writer. In each round the writer issues writes for some ! number of dirty buffers (controllable by the following parameters). ! The selected buffers will always be the ! least recently used ones among the currently dirty buffers. ! It then sleeps for bgwriter_delay milliseconds, ! and repeats. ! Note that on many systems, the effective resolution ! of sleep delays is 10 milliseconds; setting ! bgwriter_delay to a value that is ! not a multiple of 10 may have the same results as setting it ! to the next higher multiple of 10. This option can only be set at server start or in the postgresql.conf file. --- 1206,1221 ---- Specifies the delay between activity rounds for the ! background writer. In each round the writer issues writes ! for some number of dirty buffers (controllable by the ! following parameters). The selected buffers will always be ! the least recently used ones among the currently dirty ! buffers. It then sleeps for bgwriter_delay ! milliseconds, and repeats. The default value is 200. Note ! that on many systems, the effective resolution of sleep ! delays is 10 milliseconds; setting bgwriter_delay ! to a value that is not a multiple of 10 may have the same ! results as setting it to the next higher multiple of 10. This option can only be set at server start or in the postgresql.conf file. *************** *** 1227,1236 **** bgwriter_percent (integer) ! In each round, no more than this percentage of the currently dirty ! buffers will be written (rounding up any fraction to the next whole ! number of buffers). ! This option can only be set at server start or in the postgresql.conf file. --- 1226,1235 ---- bgwriter_percent (integer) ! In each round, no more than this percentage of the currently ! dirty buffers will be written (rounding up any fraction to ! the next whole number of buffers). The default value is ! 1. This option can only be set at server start or in the postgresql.conf file. *************** *** 1240,1247 **** bgwriter_maxpages (integer) ! In each round, no more than this many dirty buffers will be written. ! This option can only be set at server start or in the postgresql.conf file. --- 1239,1247 ---- bgwriter_maxpages (integer) ! In each round, no more than this many dirty buffers will be ! written. The default value is 100. This option can only be ! set at server start or in the postgresql.conf file. *************** *** 1250,1258 **** Smaller values of bgwriter_percent and ! bgwriter_maxpages reduce the extra I/O load caused by ! the background writer, but leave more work to be done at checkpoint ! time. To reduce load spikes at checkpoints, increase the values. --- 1250,1259 ---- Smaller values of bgwriter_percent and ! bgwriter_maxpages reduce the extra I/O load ! caused by the background writer, but leave more work to be done ! at checkpoint time. To reduce load spikes at checkpoints, ! increase the values. *************** *** 1448,1454 **** It is important for the command to return a zero exit status only if ! it succeeds. Examples: archive_command = 'cp "%p" /mnt/server/archivedir/"%f"' archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32 --- 1449,1455 ---- It is important for the command to return a zero exit status only if ! it succeeds. Examples: archive_command = 'cp "%p" /mnt/server/archivedir/"%f"' archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32 *************** *** 1880,1893 **** log_destination (string) ! PostgreSQL supports several methods ! for logging server messages, including ! stderr and ! syslog. On Windows, ! eventlog is also supported. Set this ! option to a list of desired log destinations separated by ! commas. The default is to log to stderr ! only. This option can only be set at server start or in the postgresql.conf configuration file. --- 1881,1894 ---- log_destination (string) ! PostgreSQL supports several methods ! for logging server messages, including ! stderr and ! syslog. On Windows, ! eventlog is also supported. Set this ! option to a list of desired log destinations separated by ! commas. The default is to log to stderr ! only. This option can only be set at server start or in the postgresql.conf configuration file. *************** *** 1898,1911 **** redirect_stderr (boolean) ! This option allows messages sent to stderr to be ! captured and redirected into log files. ! This option, in combination with logging to stderr, ! is often more useful than ! logging to syslog, since some types of messages ! may not appear in syslog output (a common example ! is dynamic-linker failure messages). ! This option can only be set at server start. --- 1899,1912 ---- redirect_stderr (boolean) ! This option allows messages sent to stderr to be ! captured and redirected into log files. ! This option, in combination with logging to stderr, ! is often more useful than ! logging to syslog, since some types of messages ! may not appear in syslog output (a common example ! is dynamic-linker failure messages). ! This option can only be set at server start. *************** *** 1914,1923 **** log_directory (string) ! When redirect_stderr is enabled, this option determines the directory in which log files will be created. ! It may be specified as an absolute path, or relative to the ! cluster data directory. This option can only be set at server start or in the postgresql.conf configuration file. --- 1915,1924 ---- log_directory (string) ! When redirect_stderr is enabled, this option determines the directory in which log files will be created. ! It may be specified as an absolute path, or relative to the ! cluster data directory. This option can only be set at server start or in the postgresql.conf configuration file. *************** *** 1928,1937 **** log_filename_prefix (string) ! When redirect_stderr is enabled, this option sets the prefix of the file names of the created log files. ! The postmaster PID and the current time are appended to this ! prefix to form an exact log file name. This option can only be set at server start or in the postgresql.conf configuration file. --- 1929,1938 ---- log_filename_prefix (string) ! When redirect_stderr is enabled, this option sets the prefix of the file names of the created log files. ! The postmaster PID and the current time are appended to this ! prefix to form an exact log file name. This option can only be set at server start or in the postgresql.conf configuration file. *************** *** 1942,1952 **** log_rotation_age (integer) ! When redirect_stderr is enabled, this option ! determines the maximum lifetime of an individual log file. ! After this many minutes have elapsed, a new log file will ! be created. Set to zero to disable time-based creation of ! new log files. This option can only be set at server start or in the postgresql.conf configuration file. --- 1943,1953 ---- log_rotation_age (integer) ! When redirect_stderr is enabled, this option ! determines the maximum lifetime of an individual log file. ! After this many minutes have elapsed, a new log file will ! be created. Set to zero to disable time-based creation of ! new log files. This option can only be set at server start or in the postgresql.conf configuration file. *************** *** 1957,1967 **** log_rotation_size (integer) ! When redirect_stderr is enabled, this option ! determines the maximum size of an individual log file. ! After this many kilobytes have been emitted into a log file, ! a new log file will be created. Set to zero to disable size-based ! creation of new log files. This option can only be set at server start or in the postgresql.conf configuration file. --- 1958,1968 ---- log_rotation_size (integer) ! When redirect_stderr is enabled, this option ! determines the maximum size of an individual log file. ! After this many kilobytes have been emitted into a log file, ! a new log file will be created. Set to zero to disable size-based ! creation of new log files. This option can only be set at server start or in the postgresql.conf configuration file. *************** *** 1981,1987 **** the default is LOCAL0. See also the documentation of your system's syslog daemon. ! This option can only be set at server start. --- 1982,1988 ---- the default is LOCAL0. See also the documentation of your system's syslog daemon. ! This option can only be set at server start. *************** *** 1995,2001 **** PostgreSQL messages in syslog logs. The default is postgres. ! This option can only be set at server start. --- 1996,2002 ---- PostgreSQL messages in syslog logs. The default is postgres. ! This option can only be set at server start. *************** *** 2107,2115 **** terminals are disassociated (same effect as postmaster's option). The server's standard output and standard error are redirected ! to /dev/null, so any messages sent to them will be lost. ! Unless syslog logging is selected or ! redirect_stderr is enabled, using this option is discouraged because it makes it impossible to see error messages. --- 2108,2116 ---- terminals are disassociated (same effect as postmaster's option). The server's standard output and standard error are redirected ! to /dev/null, so any messages sent to them will be lost. ! Unless syslog logging is selected or ! redirect_stderr is enabled, using this option is discouraged because it makes it impossible to see error messages. *************** *** 2271,2365 **** log_line_prefix (string) ! This is a printf-style string that is output at the ! beginning of each log line. The default is an empty string. ! Each recognized escape is replaced as outlined ! below - anything else that looks like an escape is ignored. Other ! characters are copied straight to the log line. Some escapes are ! only recognised by session processes, and do not apply to ! background processes such as the postmaster. Syslog produces its own ! timestamp and process ID information, so you probably do not want to ! use those escapes if you are using syslog. ! This option can only be set at server start or in the postgresql.conf configuration file. ! ! ! ! ! Escape ! Effect ! Session only ! ! ! ! ! %u ! User Name ! Yes ! ! ! %d ! Database Name ! Yes ! ! ! %r ! Remote Hostname or IP address, and Remote Port ! Yes ! ! ! %p ! Process ID ! No ! ! ! %t ! Timestamp ! No ! ! ! %i ! Command Tag. This is the command which generated the log ! line. ! Yes ! ! ! %c ! Session ID. A unique identifier for each session. ! It is 2 4-byte hexadecimal numbers (without leading zeros) separated by a dot. The numbers ! are the Session Start Time and the Process ID, so this can also ! be used as a space saving way of printing these items. ! Yes ! ! ! %l ! Number of the log line for each process, ! starting at 1 ! No ! ! ! %s ! Session Start Timestamp ! Yes ! ! ! %x ! Does not produce any output, but tells non-session ! processes to stop at this point in the string. Ignored by ! session processes. ! No ! ! ! %% ! Literal % ! No ! ! ! ! --- 2272,2366 ---- log_line_prefix (string) ! This is a printf-style string that is output at the ! beginning of each log line. The default is an empty string. ! Each recognized escape is replaced as outlined ! below - anything else that looks like an escape is ignored. Other ! characters are copied straight to the log line. Some escapes are ! only recognised by session processes, and do not apply to ! background processes such as the postmaster. Syslog produces its own ! timestamp and process ID information, so you probably do not want to ! use those escapes if you are using syslog. ! This option can only be set at server start or in the postgresql.conf configuration file. ! ! ! ! ! Escape ! Effect ! Session only ! ! ! ! ! %u ! User Name ! Yes ! ! ! %d ! Database Name ! Yes ! ! ! %r ! Remote Hostname or IP address, and Remote Port ! Yes ! ! ! %p ! Process ID ! No ! ! ! %t ! Timestamp ! No ! ! ! %i ! Command Tag. This is the command which generated the log ! line. ! Yes ! ! ! %c ! Session ID. A unique identifier for each session. ! It is 2 4-byte hexadecimal numbers (without leading zeros) separated by a dot. The numbers ! are the Session Start Time and the Process ID, so this can also ! be used as a space saving way of printing these items. ! Yes ! ! ! %l ! Number of the log line for each process, ! starting at 1 ! No ! ! ! %s ! Session Start Timestamp ! Yes ! ! ! %x ! Does not produce any output, but tells non-session ! processes to stop at this point in the string. Ignored by ! session processes. ! No ! ! ! %% ! Literal % ! No ! ! ! ! *************** *** 2861,2867 **** The value for dynamic_library_path has to be a list of absolute directory paths separated by colons (or semi-colons ! on Windows). If a list element starts with the special string $libdir, the compiled-in PostgreSQL package library directory is substituted for $libdir. This --- 2862,2868 ---- The value for dynamic_library_path has to be a list of absolute directory paths separated by colons (or semi-colons ! on Windows). If a list element starts with the special string $libdir, the compiled-in PostgreSQL package library directory is substituted for $libdir. This *************** *** 3138,3145 **** Shows the locale in which sorting of textual data is done. ! See for more information. ! The value is determined when the database cluster is initialized. --- 3139,3146 ---- Shows the locale in which sorting of textual data is done. ! See for more information. ! The value is determined when the database cluster is initialized. *************** *** 3149,3158 **** Shows the locale that determines character classifications. ! See for more information. ! The value is determined when the database cluster is initialized. ! Ordinarily this will be the same as lc_collate, ! but for special applications it might be set differently. --- 3150,3159 ---- Shows the locale that determines character classifications. ! See for more information. ! The value is determined when the database cluster is initialized. ! Ordinarily this will be the same as lc_collate, ! but for special applications it might be set differently. *************** *** 3240,3246 **** variable is a variable not normally known to PostgreSQL proper but used by some add-on module. Such variables must have names consisting of a class ! name, a dot, and a variable name. custom_variable_classes specifies all the class names in use in a particular installation. This option can only be set at server start or in the postgresql.conf configuration file. --- 3241,3247 ---- variable is a variable not normally known to PostgreSQL proper but used by some add-on module. Such variables must have names consisting of a class ! name, a dot, and a variable name. custom_variable_classes specifies all the class names in use in a particular installation. This option can only be set at server start or in the postgresql.conf configuration file. Index: doc/src/sgml/xfunc.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/xfunc.sgml,v retrieving revision 1.85 diff -c -r1.85 xfunc.sgml *** doc/src/sgml/xfunc.sgml 30 Jul 2004 12:26:39 -0000 1.85 --- doc/src/sgml/xfunc.sgml 21 Aug 2004 12:51:52 -0000 *************** *** 1618,1634 **** ! If you are thinking about distributing your PostgreSQL extension ! modules, setting up a portable build system for them can be fairly ! difficult. Therefore the PostgreSQL installation provides a build infrastructure for extensions, called PGXS, so that simple extension modules can be built simply against an already installed server. Note that this infrastructure is not intended to be a universal build system framework that can be used ! to build all software interfacing to PostgreSQL; it simply ! automates common build rules for simple server extension modules. ! For more complicated packages, you need to write your own build ! system. --- 1618,1635 ---- ! If you are thinking about distributing your ! PostgreSQL extension modules, setting up a ! portable build system for them can be fairly difficult. Therefore ! the PostgreSQL installation provides a build infrastructure for extensions, called PGXS, so that simple extension modules can be built simply against an already installed server. Note that this infrastructure is not intended to be a universal build system framework that can be used ! to build all software interfacing to PostgreSQL; ! it simply automates common build rules for simple server extension ! modules. For more complicated packages, you need to write your ! own build system. *************** *** 1807,1820 **** Composite-Type Arguments in C-Language Functions ! Composite types do not have a fixed layout like C ! structures. Instances of a composite type may contain ! null fields. In addition, composite types that are ! part of an inheritance hierarchy may have different ! fields than other members of the same inheritance hierarchy. ! Therefore, PostgreSQL provides ! a function interface for accessing fields of composite types ! from C. --- 1808,1820 ---- Composite-Type Arguments in C-Language Functions ! Composite types do not have a fixed layout like C structures. ! Instances of a composite type may contain null fields. In ! addition, composite types that are part of an inheritance ! hierarchy may have different fields than other members of the ! same inheritance hierarchy. Therefore, ! PostgreSQL provides a function ! interface for accessing fields of composite types from C. Index: doc/src/sgml/ref/alter_index.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/alter_index.sgml,v retrieving revision 1.3 diff -c -r1.3 alter_index.sgml *** doc/src/sgml/ref/alter_index.sgml 21 Aug 2004 16:16:04 -0000 1.3 --- doc/src/sgml/ref/alter_index.sgml 22 Aug 2004 21:13:23 -0000 *************** *** 167,173 **** Compatibility ! ALTER INDEX is a PostgreSQL extension. --- 167,174 ---- Compatibility ! ALTER INDEX is a PostgreSQL ! extension. Index: doc/src/sgml/ref/alter_sequence.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/alter_sequence.sgml,v retrieving revision 1.7 diff -c -r1.7 alter_sequence.sgml *** doc/src/sgml/ref/alter_sequence.sgml 29 Nov 2003 19:51:38 -0000 1.7 --- doc/src/sgml/ref/alter_sequence.sgml 21 Aug 2004 20:54:48 -0000 *************** *** 14,20 **** ALTER SEQUENCE ! alter the definition of a sequence generator --- 14,20 ---- ALTER SEQUENCE ! change the definition of a sequence generator Index: doc/src/sgml/ref/create_table_as.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/create_table_as.sgml,v retrieving revision 1.22 diff -c -r1.22 create_table_as.sgml *** doc/src/sgml/ref/create_table_as.sgml 4 Aug 2004 21:33:42 -0000 1.22 --- doc/src/sgml/ref/create_table_as.sgml 21 Aug 2004 20:55:17 -0000 *************** *** 11,17 **** CREATE TABLE AS ! create a new table from the results of a query --- 11,17 ---- CREATE TABLE AS ! define a new table from the results of a query Index: doc/src/sgml/ref/create_tablespace.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/create_tablespace.sgml,v retrieving revision 1.3 diff -c -r1.3 create_tablespace.sgml *** doc/src/sgml/ref/create_tablespace.sgml 2 Aug 2004 04:25:37 -0000 1.3 --- doc/src/sgml/ref/create_tablespace.sgml 21 Aug 2004 19:57:35 -0000 *************** *** 34,41 **** ! A tablespace allows superusers to define an alternative location on the ! file system where the data files representing database objects (such as tables and indexes) may reside. --- 34,41 ---- ! A tablespace allows superusers to define an alternative location on ! the file system where the data files containing database objects (such as tables and indexes) may reside. Index: doc/src/sgml/ref/psql-ref.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/psql-ref.sgml,v retrieving revision 1.120 diff -c -r1.120 psql-ref.sgml *** doc/src/sgml/ref/psql-ref.sgml 14 Aug 2004 23:49:07 -0000 1.120 --- doc/src/sgml/ref/psql-ref.sgml 21 Aug 2004 12:43:46 -0000 *************** *** 771,777 **** Shows the copyright and distribution terms of ! PostgreSQL. --- 771,777 ---- Shows the copyright and distribution terms of ! PostgreSQL. Index: doc/src/sgml/ref/release_savepoint.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/release_savepoint.sgml,v retrieving revision 1.1 diff -c -r1.1 release_savepoint.sgml *** doc/src/sgml/ref/release_savepoint.sgml 12 Aug 2004 19:12:21 -0000 1.1 --- doc/src/sgml/ref/release_savepoint.sgml 21 Aug 2004 20:08:03 -0000 *************** *** 77,83 **** It is not possible to release a savepoint when the transaction is in ! aborted state. --- 77,83 ---- It is not possible to release a savepoint when the transaction is in ! an aborted state. *************** *** 108,116 **** Compatibility ! The SQL2003 standard specifies that the keyword SAVEPOINT is mandatory. ! PostgreSQL allows the SAVEPOINT keyword to be ! omitted. Otherwise, this command is fully conforming. --- 108,118 ---- Compatibility ! The SQL2003 standard specifies that the keyword ! SAVEPOINT is mandatory. ! PostgreSQL allows the ! SAVEPOINT keyword to be omitted. Otherwise, this ! command is fully conforming. Index: doc/src/sgml/ref/rollback_to.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/rollback_to.sgml,v retrieving revision 1.2 diff -c -r1.2 rollback_to.sgml *** doc/src/sgml/ref/rollback_to.sgml 12 Aug 2004 19:12:21 -0000 1.2 --- doc/src/sgml/ref/rollback_to.sgml 21 Aug 2004 20:54:02 -0000 *************** *** 128,140 **** Compatibility ! The SQL2003 standard specifies that the keyword SAVEPOINT is mandatory. ! PostgreSQL and Oracle ! allow the SAVEPOINT keyword to be omitted. SQL2003 allows only ! WORK, not TRANSACTION, as a noise word after ROLLBACK. Also, SQL2003 ! has an optional clause AND [ NO ] CHAIN which is not currently supported ! by PostgreSQL. Otherwise, this command is ! fully conforming. --- 128,142 ---- Compatibility ! The SQL2003 standard specifies that the keyword ! SAVEPOINT is mandatory. PostgreSQL and ! Oracle allow the SAVEPOINT ! keyword to be omitted. SQL2003 allows only WORK, not ! TRANSACTION, as a noise word after ! ROLLBACK. Also, SQL2003 has an optional clause ! AND [ NO ] CHAIN which is not currently supported by ! PostgreSQL. Otherwise, this command is fully ! conforming. Index: doc/src/sgml/ref/select_into.sgml =================================================================== RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/select_into.sgml,v retrieving revision 1.29 diff -c -r1.29 select_into.sgml *** doc/src/sgml/ref/select_into.sgml 4 Aug 2004 21:33:42 -0000 1.29 --- doc/src/sgml/ref/select_into.sgml 21 Aug 2004 20:56:36 -0000 *************** *** 11,17 **** SELECT INTO ! create a new table from the results of a query --- 11,17 ---- SELECT INTO ! define a new table from the results of a query