diff --git a/doc/src/sgml/array.sgml b/doc/src/sgml/array.sgml index fc87fdf43f0..4392b51f93b 100644 --- a/doc/src/sgml/array.sgml +++ b/doc/src/sgml/array.sgml @@ -1,4 +1,4 @@ - + Arrays @@ -76,13 +76,45 @@ CREATE TABLE tictactoe ( Array Value Input - - Now we can show some INSERT statements. To write an array - value as a literal constant, we enclose the element values within curly - braces and separate them by commas. (If you know C, this is not unlike the - C syntax for initializing structures.) We may put double quotes around any - element value, and must do so if it contains commas or curly braces. - (More details appear below.) + + array + constant + + + + To write an array value as a literal constant, enclose the element + values within curly braces and separate them by commas. (If you + know C, this is not unlike the C syntax for initializing + structures.) You may put double quotes around any element value, + and must do so if it contains commas or curly braces. (More + details appear below.) Thus, the general format of an array + constant is the following: + +'{ val1 delim val2 delim ... }' + + where delim is the delimiter character + for the type, as recorded in its pg_type entry. + (For all built-in types, this is the comma character + ,.) Each + val is either a constant of the array + element type, or a subarray. An example of an array constant is + +'{{1,2,3},{4,5,6},{7,8,9}}' + + This constant is a two-dimensional, 3-by-3 array consisting of + three subarrays of integers. + + + + (These kinds of array constants are actually only a special case of + the generic type constants discussed in . The constant is initially + treated as a string and passed to the array input conversion + routine. An explicit type specification might be necessary.) + + + + Now we can show some INSERT statements. INSERT INTO sal_emp @@ -95,14 +127,15 @@ INSERT INTO sal_emp '{20000, 25000, 25000, 25000}', '{{"talk", "consult"}, {"meeting"}}'); - + + + + A limitation of the present array implementation is that individual + elements of an array cannot be SQL null values. The entire array + can be set to null, but you can't have an array with some elements + null and some not. + - - A limitation of the present array implementation is that individual - elements of an array cannot be SQL null values. The entire array can be set - to null, but you can't have an array with some elements null and some - not. - This can lead to surprising results. For example, the result of the previous two inserts looks like this: diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index fc394219eb0..6a3556f5a16 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -1,5 +1,5 @@ Backup and Restore @@ -155,8 +155,9 @@ pg_dump -h host1 dbname | psql -h h - Restore performance can be improved by increasing SORT_MEM - (see ). + Restore performance can be improved by increasing the + configuration parameter sort_mem (see ). @@ -333,12 +334,9 @@ tar -cf backup.tar /usr/local/pgsql/data going on. For this reason it is also not advisable to trust file systems that claim to support consistent snapshots. Information about stopping the server can be - found in . - - - - Needless to say that you also need to shut down the server - before restoring the data. + found in . Needless to say + that you also need to shut down the server before restoring the + data. @@ -362,7 +360,18 @@ tar -cf backup.tar /usr/local/pgsql/data - Also note that the file system backup will not necessarily be + An alternative file-system backup approach is to make a + consistent snapshot of the data directory, if the + file system supports that functionality. Such a snapshot will save + the database files in a state where the database server was not + properly shut down; therefore, when you start the database server + on this backed up directory, it will think the server had crashed + and replay the WAL log. This is not a problem, just be aware of + it. + + + + Note that the file system backup will not necessarily be smaller than an SQL dump. On the contrary, it will most likely be larger. (pg_dump does not need to dump the contents of indexes for example, just the commands to recreate @@ -372,7 +381,7 @@ tar -cf backup.tar /usr/local/pgsql/data - Migration between releases + Migration Between Releases upgrading @@ -385,17 +394,20 @@ tar -cf backup.tar /usr/local/pgsql/data As a general rule, the internal data storage format is subject to - change between releases of PostgreSQL. This does not - apply to different patch levels, 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, then you can simply reuse the - data area in disk by the new executables. Otherwise you need to + change between major releases of PostgreSQL (where + the number after the first dot changes). This does not apply to + different minor releases under the same major release (where the + number of 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, then you can simply reuse the data + area in disk by the new executables. Otherwise you need to back up your data and restore it on the new server, using pg_dump. (There are checks in place that prevent you from doing the wrong thing, so no harm can be done by confusing these things.) The precise installation procedure is - not subject of this section; these details are in . + not subject of this section; these details are in . diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index f7cef0ce4be..fb789d558d5 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -1,4 +1,4 @@ - + Localization</> @@ -248,12 +248,9 @@ initdb --locale=sv_SE <para> Client applications that handle server-side errors by parsing the text of the error message will obviously have problems when the - server's messages are in a different language. If you create such - an application you need to devise a plan to cope with this - situation. The embedded SQL interface (<application>ECPG</>) is - also affected by this problem. It is currently recommended that - servers interfacing with <application>ECPG</> applications be - configured to send messages in English. + server's messages are in a different language. Authors of such + applications are advised to make use of the error code scheme + instead. </para> <para> @@ -430,7 +427,7 @@ initdb --locale=sv_SE mistakenly meant ISO 8859-5. From 7.2 on, <literal>LATIN5</> means ISO 8859-9. If you have a <literal>LATIN5</> database created on 7.1 or earlier and want to migrate to 7.2 or later, - you should be very careful about this change. + you should be careful about this change. </para> </important> diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml index 445b8f4c356..ca736274eee 100644 --- a/doc/src/sgml/client-auth.sgml +++ b/doc/src/sgml/client-auth.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.59 2003/09/13 16:43:38 momjian Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.60 2003/11/04 09:55:38 petere Exp $ --> <chapter id="client-authentication"> @@ -85,13 +85,13 @@ $Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.59 2003/09/13 16:43:38 <para> A record may have one of the seven formats <synopsis> -local <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> -host <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable> <replaceable>IP-mask</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> -hostssl <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable> <replaceable>IP-mask</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> +local <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> +host <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable> <replaceable>IP-mask</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> +hostssl <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable> <replaceable>IP-mask</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable> <replaceable>IP-mask</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> -host <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable>/<replaceable>CIDR-mask</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> -hostssl <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable>/<replaceable>CIDR-mask</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> -hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable>/<replaceable>CIDR-mask</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> +host <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable>/<replaceable>IP-masklen</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> +hostssl <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable>/<replaceable>IP-masklen</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> +hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable>/<replaceable>IP-masklen</replaceable> <replaceable>authentication-method</replaceable> <optional><replaceable>authentication-option</replaceable></optional> </synopsis> The meaning of the fields is as follows: @@ -220,25 +220,26 @@ hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable> </varlistentry> <varlistentry> - <term><replaceable>CIDR-mask</replaceable></term> + <term><replaceable>IP-masklen</replaceable></term> <listitem> <para> - This field may be used as an alternative to the - <replaceable>IP-mask</replaceable> notation. It is an - integer specifying the number of high-order bits - to set in the mask. The number must - be between 0 and 32 (in the case of an IPv4 address) or 128 - (in the case of an IPv6 address) inclusive. 0 will match any - address, while 32/128 will match only the exact host specified. - The same matching logic is used as for a dotted notation - <replaceable>IP-Mask</replaceable>. + This field may be used as an alternative to the + <replaceable>IP-mask</replaceable> notation. It is an integer + specifying the number of high-order bits to set in the mask. + The number must be between 0 and 32 (in the case of an IPv4 + address) or 128 (in the case of an IPv6 address) inclusive. 0 + will match any address, while 32 (or 128, respectively) will + match only the exact host specified. The same matching logic + is used as for a dotted notation + <replaceable>IP-mask</replaceable>. </para> <para> - There must be no white space between the <replaceable>IP-address</replaceable> - and the <literal>/</literal> or the <literal>/</literal> and the - <replaceable>CIDR-mask</replaceable>, or the file will not be parsed - correctly. + There must be no white space between the + <replaceable>IP-address</replaceable> and the + <literal>/</literal> or the <literal>/</literal> and the + <replaceable>IP-masklen</replaceable>, or the file will not be + parsed correctly. </para> <para> diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 2c9a45e8adb..933178ff1dd 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.128 2003/11/01 01:56:29 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.129 2003/11/04 09:55:38 petere Exp $ --> <chapter id="datatype"> @@ -917,10 +917,10 @@ CREATE TABLE <replaceable class="parameter">tablename</replaceable> ( <para> In addition, <productname>PostgreSQL</productname> provides the - <type>text</type> type, which stores strings of any - length. Although the type <type>text</type> is not in the - <acronym>SQL</acronym> standard, several other SQL database products - have it as well. + <type>text</type> type, which stores strings of any length. + Although the type <type>text</type> is not in the + <acronym>SQL</acronym> standard, several other SQL database + management systems have it as well. </para> <para> @@ -1464,7 +1464,7 @@ SELECT b, char_length(b) FROM test2; </row> <row> <entry>1999-01-08</entry> - <entry>ISO-8601, January 8 in any mode + <entry>ISO 8601, January 8 in any mode (recommended format)</entry> </row> <row> @@ -1486,11 +1486,11 @@ SELECT b, char_length(b) FROM test2; </row> <row> <entry>19990108</entry> - <entry>ISO-8601; January 8, 1999 in any mode</entry> + <entry>ISO 8601; January 8, 1999 in any mode</entry> </row> <row> <entry>990108</entry> - <entry>ISO-8601; January 8, 1999 in any mode</entry> + <entry>ISO 8601; January 8, 1999 in any mode</entry> </row> <row> <entry>1999.008</entry> diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index 855369dbb66..e224d3c5139 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -1,4 +1,4 @@ -<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ddl.sgml,v 1.21 2003/11/01 01:56:29 petere Exp $ --> +<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ddl.sgml,v 1.22 2003/11/04 09:55:38 petere Exp $ --> <chapter id="ddl"> <title>Data Definition @@ -318,12 +318,12 @@ DROP TABLE products; - Transaction identifiers are also 32-bit quantities. In a long-lived - database it is possible for transaction IDs to wrap around. This - is not a fatal problem given appropriate maintenance procedures; - see for details. However, it is - unwise to depend on uniqueness of transaction IDs over the long term - (more than one billion transactions). + Transaction identifiers are also 32-bit quantities. In a + long-lived database it is possible for transaction IDs to wrap + around. This is not a fatal problem given appropriate maintenance + procedures; see for details. It is + unwise, however, to depend on the uniqueness of transaction IDs + over the long term (more than one billion transactions). diff --git a/doc/src/sgml/features.sgml b/doc/src/sgml/features.sgml index 09e08960202..093612b6314 100644 --- a/doc/src/sgml/features.sgml +++ b/doc/src/sgml/features.sgml @@ -1,5 +1,5 @@ @@ -30,7 +30,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.20 2003/09/20 20:12:04 tg SQL92 defined three feature sets for conformance: - Entry, Intermediate, and Full. Most database products claiming + Entry, Intermediate, and Full. Most database management systems claiming SQL standard conformance were conforming at only the Entry level, since the entire set of features in the Intermediate and Full levels was either too voluminous or in diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 71373bbd19d..cf1c1a16130 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -1,5 +1,5 @@ @@ -29,10 +29,10 @@ PostgreSQL documentation the functions and operators described in this chapter, with the exception of the most trivial arithmetic and comparison operators and some explicitly marked functions, are not specified by the - SQL - standard. Some of the extended functionality is present in other - SQL implementations, and in many cases this - functionality is compatible and consistent between various products. + SQL standard. Some of the extended functionality + is present in other SQL database management + systems, and in many cases this functionality is compatible and + consistent between the various implementations. @@ -7176,7 +7176,7 @@ SELECT pg_type_is_visible('myschema.widget'::regtype); - Array Functions + Array Functions and Operators shows the operators @@ -7578,22 +7578,23 @@ SELECT pg_type_is_visible('myschema.widget'::regtype); - Users accustomed to working with other RDBMS products may be - surprised by the performance characteristics of certain aggregate - functions in PostgreSQL when the - aggregate is applied to the entire table (in other words, no - WHERE clause is specified). In particular, - a query like + Users accustomed to working with other SQL database management + systems may be surprised by the performance characteristics of + certain aggregate functions in + PostgreSQL when the aggregate is + applied to the entire table (in other words, no + WHERE clause is specified). In particular, a + query like SELECT min(col) FROM sometable; - will be executed by PostgreSQL using a - sequential scan of the entire table. Other database systems may - optimize queries of this form to use an index on the column, if one - is available. Similarly, the aggregate functions - max() and count() always - require a sequential scan if applied to the entire table in - PostgreSQL. + will be executed by PostgreSQL using a + sequential scan of the entire table. Other database systems may + optimize queries of this form to use an index on the column, if + one is available. Similarly, the aggregate functions + max() and count() always + require a sequential scan if applied to the entire table in + PostgreSQL. @@ -7602,8 +7603,8 @@ SELECT min(col) FROM sometable; queries. Since min(), max(), and count() are defined using a generic API for aggregate functions, there is no - provision for special-casing the execution of these - functions under certain circumstances. + provision for special-casing the execution of these functions + under certain circumstances. diff --git a/doc/src/sgml/install-win32.sgml b/doc/src/sgml/install-win32.sgml index 9ba8f05cabd..7beb5ea97d1 100644 --- a/doc/src/sgml/install-win32.sgml +++ b/doc/src/sgml/install-win32.sgml @@ -1,5 +1,5 @@ @@ -109,27 +109,27 @@ $Header: /cvsroot/pgsql/doc/src/sgml/install-win32.sgml,v 1.14 2003/09/30 01:26: psql is compiled as a console - application. As - the Win32 console windows use a different encoding than the rest of the - system, you must take special care when using 8-bit characters (eg. German - umlauts) at the psql prompt. When - psql detects a problematic console codepage, it - will warn you at startup. To change the console codepage, two things are - neccessary: + application. As the Win32 console windows use a different + encoding than the rest of the system, you must take special care + when using 8-bit characters at the psql + prompt. When psql detects a problematic + console code page, it will warn you at startup. To change the + console code page, two things are neccessary: - Set the codepage with cmd.exe /c chcp 1252 - (1252 is the German value, replace it with your value). If you are using - cygwin, you can put this command in /etc/profile. + Set the code page by entering cmd.exe /c chcp + 1252. (1252 is a code page that is appropriate for + German; replace it with your value.) If you are using Cygwin, + you can put this command in /etc/profile. - Set the console font to Lucida Console, because the raster font - does not work with the ANSI codepage. + Set the console font to Lucida Console, because the + raster font does not work with the ANSI code page. diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml index fdad743b18e..8d25a3553da 100644 --- a/doc/src/sgml/installation.sgml +++ b/doc/src/sgml/installation.sgml @@ -1,4 +1,4 @@ - + <![%standalone-include[<productname>PostgreSQL</>]]> @@ -333,7 +333,7 @@ JAVACMD=$JAVA_HOME/bin/java <para> The <productname>PostgreSQL</> &version; sources can be obtained by anonymous FTP from <ulink - url="ftp://ftp.postgresql.org/pub/postgresql-&version;.tar.gz"></ulink>. + url="ftp://ftp.postgresql.org/pub/source/v&version;/postgresql-&version;.tar.gz"></ulink>. Use a mirror if possible. After you have obtained the file, unpack it: <screen> <userinput>gunzip postgresql-&version;.tar.gz</userinput> @@ -637,7 +637,7 @@ JAVACMD=$JAVA_HOME/bin/java <note> <para> Care has been taken to make it possible to install - <productname>PostgreSQL</> + <productname>PostgreSQL</> into shared installation locations (such as <filename>/usr/local/include</filename>) without interfering with the namespace of the rest of the system. First, the @@ -674,7 +674,7 @@ JAVACMD=$JAVA_HOME/bin/java directories that will be added to the list the compiler searches for header files. If you have optional packages (such as GNU <application>Readline</>) installed in a non-standard - location, + location, you have to use this option and probably also the corresponding <option>--with-libraries</> option. </para> @@ -732,8 +732,8 @@ JAVACMD=$JAVA_HOME/bin/java be changed later on, but if you specify it here then both server and clients will have the same default compiled in, which can be very convenient. Usually the only good reason - to select a non-default value is if you intend to run multiple - <productname>PostgreSQL</> servers on the same machine. + to select a non-default value is if you intend to run multiple + <productname>PostgreSQL</> servers on the same machine. </para> </listitem> </varlistentry> @@ -873,8 +873,8 @@ JAVACMD=$JAVA_HOME/bin/java <term><option>--with-pam</option></term> <listitem> <para> - Build with <acronym>PAM</><indexterm><primary>PAM</></> - (Pluggable Authentication Modules) support. + Build with <acronym>PAM</><indexterm><primary>PAM</></> + (Pluggable Authentication Modules) support. </para> </listitem> </varlistentry> @@ -894,7 +894,7 @@ JAVACMD=$JAVA_HOME/bin/java <term><option>--with-rendezvous</option></term> <listitem> <para> - Build with Rendezvous support. + Build with Rendezvous support. </para> </listitem> </varlistentry> @@ -903,10 +903,11 @@ JAVACMD=$JAVA_HOME/bin/java <term><option>--disable-spinlocks</option></term> <listitem> <para> - Allows source builds to succeed without CPU spinlock support. - Lack of spinlock support will produce poor performance. - This option is to be used only by platforms lacking - spinlock support. + Allow the builds to succeed even if PostgreSQL has no CPU + spinlock support for the platform. The lack of spinlock + support will result in poor performance; therefore, this + option should only be used if the build aborts and informs + you that the platform lacks spinlock support. </para> </listitem> </varlistentry> @@ -915,9 +916,10 @@ JAVACMD=$JAVA_HOME/bin/java <term><option>--enable-thread-safety</option></term> <listitem> <para> - Allow separate threads in <application>libpq</application> - and <application>ECPG</application> programs to safely - control their private connection handles. + Make the client libraries thread-safe. This allows + concurrent threads in <application>libpq</application> and + <application>ECPG</application> programs to safely control + their private connection handles. </para> </listitem> </varlistentry> @@ -941,13 +943,13 @@ JAVACMD=$JAVA_HOME/bin/java Compiles all programs and libraries with debugging symbols. This means that you can run the programs through a debugger to analyze problems. This enlarges the size of the installed - executables considerably, and on non-GCC compilers it usually - also disables compiler optimization, causing slowdowns. However, - having the symbols available is extremely helpful for dealing - with any problems that may arise. Currently, this option is - recommended for production installations only if you use GCC. - But you should always have it on if you are doing development work - or running a beta version. + executables considerably, and on non-GCC compilers it usually + also disables compiler optimization, causing slowdowns. However, + having the symbols available is extremely helpful for dealing + with any problems that may arise. Currently, this option is + recommended for production installations only if you use GCC. + But you should always have it on if you are doing development work + or running a beta version. </para> </listitem> </varlistentry> @@ -956,16 +958,16 @@ JAVACMD=$JAVA_HOME/bin/java <term><option>--enable-cassert</option></term> <listitem> <para> - Enables <firstterm>assertion</> checks in the server, which test for - many <quote>can't happen</> conditions. This is invaluable for - code development purposes, but the tests slow things down a little. - Also, having the tests turned on won't necessarily enhance the - stability of your server! The assertion checks are not categorized - for severity, and so what might be a relatively harmless bug will - still lead to server restarts if it triggers an assertion - failure. Currently, this option is not recommended for + Enables <firstterm>assertion</> checks in the server, which test for + many <quote>can't happen</> conditions. This is invaluable for + code development purposes, but the tests slow things down a little. + Also, having the tests turned on won't necessarily enhance the + stability of your server! The assertion checks are not categorized + for severity, and so what might be a relatively harmless bug will + still lead to server restarts if it triggers an assertion + failure. Currently, this option is not recommended for production use, but you should have it on for development work - or when running a beta version. + or when running a beta version. </para> </listitem> </varlistentry> @@ -974,12 +976,12 @@ JAVACMD=$JAVA_HOME/bin/java <term><option>--enable-depend</option></term> <listitem> <para> - Enables automatic dependency tracking. With this option, the - makefiles are set up so that all affected object files will - be rebuilt when any header file is changed. This is useful - if you are doing development work, but is just wasted overhead - if you intend only to compile once and install. At present, - this option will work only if you use GCC. + Enables automatic dependency tracking. With this option, the + makefiles are set up so that all affected object files will + be rebuilt when any header file is changed. This is useful + if you are doing development work, but is just wasted overhead + if you intend only to compile once and install. At present, + this option will work only if you use GCC. </para> </listitem> </varlistentry> @@ -1040,8 +1042,6 @@ All of PostgreSQL is successfully made. Ready to install. <userinput>gmake check</userinput> </screen> (This won't work as root; do it as an unprivileged user.) - It is possible that some tests fail, due to differences in error - message wording or floating point results. <![%standalone-include[The file <filename>src/test/regress/README</> and the documentation contain]]> @@ -1156,28 +1156,6 @@ All of PostgreSQL is successfully made. Ready to install. <sect1 id="install-post"> <title>Post-Installation Setup - - Tuning - - - tuning - - - - By default, PostgreSQL is configured to run on minimal - hardware. This allows it to start up with almost any hardware - configuration. However, the default configuration is not designed for - optimum performance. To achieve optimum performance, several server - variables must be adjusted, the two most common being - shared_buffers and sort_mem - mentioned in - ]]>. - Other parameters in - ]]> - also affect performance. - - - Shared Libraries @@ -1458,39 +1436,28 @@ kill `cat /usr/local/pgsql/data/postmaster.pid` - Run the regression tests against the installed server (using the - sequential test method). If you didn't run the tests before - installation, you should definitely do it now. This is also - explained in the documentation. + Run the regression tests against the installed server (using + gmake installcheck). If you didn't run the + tests before installation, you should definitely do it now. This + is also explained in the documentation. + + + By default, PostgreSQL is configured to run on + minimal hardware. This allows it to start up with almost any + hardware configuration. The default configuration is, however, + not designed for optimum performance. To achieve optimum + performance, several server parameters must be adjusted, the two + most common being shared_buffers and + sort_mem mentioned in the documentation. + Other parameters mentioned in the documentation also affect + performance. + + - - - - ]]> @@ -1519,194 +1486,186 @@ gunzip -c postgres.ps.gz \ - OS - Processor - Version - Reported - Remarks + OS + Processor + Version + Reported + Remarks - AIX - RS6000 - 7.4 - 2003-10-25, - Hans-Jürgen Schönig (hs@cybertec.at) + AIX + RS6000 + 7.4 + 2003-10-25, + Hans-Jürgen Schönig (hs@cybertec.at) see also doc/FAQ_AIX - BSD/OS - x86 - 7.4 - 2003-10-24, - Bruce Momjian (pgman@candle.pha.pa.us) + BSD/OS + x86 + 7.4 + 2003-10-24, + Bruce Momjian (pgman@candle.pha.pa.us) 4.3 - FreeBSD - Alpha - 7.4 - 2003-10-25, - Peter Eisentraut (peter_e@gmx.net) + FreeBSD + Alpha + 7.4 + 2003-10-25, + Peter Eisentraut (peter_e@gmx.net) 4.8 - FreeBSD - x86 - 7.4 - 2003-10-24, - Peter Eisentraut (peter_e@gmx.net) + FreeBSD + x86 + 7.4 + 2003-10-24, + Peter Eisentraut (peter_e@gmx.net) 4.9 - HP-UX - PA-RISC - 7.4 + HP-UX + PA-RISC + 7.4 2003-10-31, - 10.20 Tom Lane (tgl@sss.pgh.pa.us) + 10.20 Tom Lane (tgl@sss.pgh.pa.us) gcc and cc; see also doc/FAQ_HPUX - IRIX - MIPS - 7.3 - 2002-10-27, - Ian Barwick (barwick@gmx.net) - Irix64 Komma 6.5 + IRIX + MIPS + 7.3 + 2002-10-27, + Ian Barwick (barwick@gmx.net) + Irix64 Komma 6.5 - Linux - Alpha - 7.4 - 2003-10-25, - Noèl Köthe (noel@debian.org) - 2.4 + Linux + Alpha + 7.4 + 2003-10-25, + Noèl Köthe (noel@debian.org) + 2.4 - Linux - arm41 - 7.4 - 2003-10-25, - Noèl Köthe (noel@debian.org) - 2.4 + Linux + arm41 + 7.4 + 2003-10-25, + Noèl Köthe (noel@debian.org) + 2.4 - Linux - Itanium - 7.4 - 2003-10-25, - Noèl Köthe (noel@debian.org) - 2.4 + Linux + Itanium + 7.4 + 2003-10-25, + Noèl Köthe (noel@debian.org) + 2.4 - Linux - m68k - 7.4 - 2003-10-25, - Noèl Köthe (noel@debian.org) - 2.4 + Linux + m68k + 7.4 + 2003-10-25, + Noèl Köthe (noel@debian.org) + 2.4 - Linux - MIPS - 7.4 - 2003-10-25, - Noèl Köthe (noel@debian.org) - 2.4 + Linux + MIPS + 7.4 + 2003-10-25, + Noèl Köthe (noel@debian.org) + 2.4 - Linux - Opteron - 7.4 - 2003-11-01, - Jani Averbach (jaa@cc.jyu.fi) - 2.6 + Linux + Opteron + 7.4 + 2003-11-01, + Jani Averbach (jaa@cc.jyu.fi) + 2.6 - Linux - PlayStation 2 - 7.3 - 2002-11-19, - Permaine Cheung pcheung@redhat.com) - #undef HAS_TEST_AND_SET, remove slock_t typedef + Linux + PPC + 7.4 + 2003-10-25, + Noèl Köthe (noel@debian.org) + - Linux - PPC - 7.4 - 2003-10-25, - Noèl Köthe (noel@debian.org) - + Linux + S/390 + 7.4 + 2003-10-25, + Noèl Köthe (noel@debian.org) + 2.4 - Linux - S/390 - 7.4 - 2003-10-25, - Noèl Köthe (noel@debian.org) - 2.4 + Linux + Sparc + 7.4 + 2003-10-24, + Peter Eisentraut (peter_e@gmx.net) + 2.4, 32-bit - Linux - Sparc - 7.4 - 2003-10-24, - Peter Eisentraut (peter_e@gmx.net) - 2.4, 32-bit + Linux + x86 + 7.4 + 2003-10-24, + Peter Eisentraut (peter_e@gmx.net) + 2.4 - Linux - x86 - 7.4 - 2003-10-24, - Peter Eisentraut (peter_e@gmx.net) - 2.4 + MacOS X + PPC + 7.4 + 2003-10-24, + 10.2.8, Adam Witney (awitney@sghms.ac.uk), + 10.3, Marko Karppinen (marko@karppinen.fi) + - MacOS X - PPC - 7.4 - 2003-10-24, - 10.2.8, Adam Witney (awitney@sghms.ac.uk), - 10.3, Marko Karppinen (marko@karppinen.fi) - + NetBSD + arm32 + 7.3 + 2002-11-19, + Patrick Welche (prlw1@newn.cam.ac.uk) + 1.6 - NetBSD - arm32 - 7.3 - 2002-11-19, - Patrick Welche (prlw1@newn.cam.ac.uk) - 1.6 + NetBSD + x86 + 7.4 + 2003-10-24, + Peter Eisentraut (peter_e@gmx.net) + 1.6 - NetBSD - x86 - 7.4 - 2003-10-24, - Peter Eisentraut (peter_e@gmx.net) - 1.6 - - - OpenBSD - Sparc - 7.4 - 2003-11-01, - Peter Eisentraut (peter_e@gmx.net) + OpenBSD + Sparc + 7.4 + 2003-11-01, + Peter Eisentraut (peter_e@gmx.net) 3.4 - OpenBSD - x86 - 7.4 - 2003-10-24, - Peter Eisentraut (peter_e@gmx.net) + OpenBSD + x86 + 7.4 + 2003-10-24, + Peter Eisentraut (peter_e@gmx.net) 3.2 - SCO OpenServer 5 + SCO OpenServer x86 7.3.1 2002-12-11, @@ -1714,45 +1673,45 @@ gunzip -c postgres.ps.gz \ 5.0.4, gcc; see also doc/FAQ_SCO - Solaris - Sparc - 7.4 - 2003-10-26, - Christopher Browne (cbbrowne@libertyrms.info) - 2.8; see also doc/FAQ_Solaris + Solaris + Sparc + 7.4 + 2003-10-26, + Christopher Browne (cbbrowne@libertyrms.info) + 2.8; see also doc/FAQ_Solaris - Solaris - x86 - 7.4 - 2003-10-26, - Kurt Roeckx (Q@ping.be) - 2.6 see also doc/FAQ_Solaris + Solaris + x86 + 7.4 + 2003-10-26, + Kurt Roeckx (Q@ping.be) + 2.6 see also doc/FAQ_Solaris - Tru64 UNIX - Alpha - 7.4 - 2003-10-25, - 5.1b Peter Eisentraut (peter_e@gmx.net), - 4.0g Alessio Bragadini (alessio@albourne.com) + Tru64 UNIX + Alpha + 7.4 + 2003-10-25, + 5.1b Peter Eisentraut (peter_e@gmx.net), + 4.0g Alessio Bragadini (alessio@albourne.com) - UnixWare - x86 - 7.3 - 2002-11-01, - 7.1.3 Larry Rosenman (ler@lerctr.org), - 7.1.1 and 7.1.2(8.0.0) Olivier Prenant (ohp@pyrenet.fr) - see also doc/FAQ_SCO + UnixWare + x86 + 7.3 + 2002-11-01, + 7.1.3 Larry Rosenman (ler@lerctr.org), + 7.1.1 and 7.1.2(8.0.0) Olivier Prenant (ohp@pyrenet.fr) + see also doc/FAQ_SCO - Windows with Cygwin - x86 - 7.4 - 2003-10-24, - Peter Eisentraut (peter_e@gmx.net) + Windows with Cygwin + x86 + 7.4 + 2003-10-24, + Peter Eisentraut (peter_e@gmx.net) see doc/FAQ_MSWIN @@ -1804,6 +1763,26 @@ gunzip -c postgres.ps.gz \ Cyril Velter (cyril.velter@libertysurf.fr) needs updates to semaphore code + + Linux + PlayStation 2 + 7.4 + 2003-11-02, + Peter Eisentraut peter_e@gmx.net) + + needs new config.guess, + , #undef + HAS_TEST_AND_SET, disable tas_dummy() + + + + Linux + PA-RISC + 7.4 + 2003-10-25, + Noèl Köthe (noel@debian.org) + needs , otherwise OK + NetBSD Alpha diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml index 6a42552b8f9..1b248958204 100644 --- a/doc/src/sgml/maintenance.sgml +++ b/doc/src/sgml/maintenance.sgml @@ -1,5 +1,5 @@ @@ -40,10 +40,10 @@ $Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.27 2003/11/01 01:56:29 - PostgreSQL is low-maintenance compared to - some other database products. Nonetheless, appropriate attention to - these tasks will go far towards ensuring a pleasant and productive - experience with the system. + PostgreSQL is low-maintenance compared + to some other database management systems. Nonetheless, + appropriate attention to these tasks will go far towards ensuring a + pleasant and productive experience with the system. diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 2ba07811ef0..9a14777ff41 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -1,5 +1,5 @@ @@ -367,12 +367,13 @@ postgres: user database host . The per-database access - functions take a database OID as argument to identify which database to - report on. The per-table and per-index functions take a table or - index OID. (Note that only tables and indexes in the current - database can be seen with these functions.) The per-backend access - functions take a backend ID number, which ranges from one to the - number of currently active backend processes. + functions take a database OID as argument to identify which + database to report on. The per-table and per-index functions take + a table or index OID. (Note that only tables and indexes in the + current database can be seen with these functions.) The + per-backend process access functions take a backend process ID + number, which ranges from one to the number of currently active + backend processes. diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml index 2fdff8be684..e46c5928c78 100644 --- a/doc/src/sgml/mvcc.sgml +++ b/doc/src/sgml/mvcc.sgml @@ -1,5 +1,5 @@ @@ -770,22 +770,17 @@ UPDATE accounts SET balance = balance - 100.00 WHERE acctnum = 22222; To ensure the current validity of a row and protect it against - concurrent updates one must use SELECT FOR UPDATE or - an appropriate LOCK TABLE statement. - (SELECT FOR UPDATE locks just the returned rows against - concurrent updates, while LOCK TABLE locks the - whole table.) - This should be taken into account when porting applications to + concurrent updates one must use SELECT FOR + UPDATE or an appropriate LOCK TABLE + statement. (SELECT FOR UPDATE locks just the + returned rows against concurrent updates, while LOCK + 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 the above consideration is also the case when - upgrading from PostgreSQL versions - prior to 6.5. - - + (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.) diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml index 3059c63c97a..c7e0864f5ca 100644 --- a/doc/src/sgml/postgres.sgml +++ b/doc/src/sgml/postgres.sgml @@ -1,5 +1,5 @@ - Readers of this book should know how to connect to a + Readers of this part should know how to connect to a PostgreSQL database and issue SQL commands. Readers that are unfamiliar with these issues are encouraged to read diff --git a/doc/src/sgml/queries.sgml b/doc/src/sgml/queries.sgml index 276bfd63234..8a6e5fa9c2e 100644 --- a/doc/src/sgml/queries.sgml +++ b/doc/src/sgml/queries.sgml @@ -1,4 +1,4 @@ - + Queries @@ -105,7 +105,7 @@ SELECT random(); - The FROM Clause + The <literal>FROM</literal> Clause The FROM clause derives a table from one or more other @@ -670,7 +670,7 @@ SELECT * - The WHERE Clause + The <literal>WHERE</literal> Clause WHERE @@ -716,7 +716,7 @@ FROM a NATURAL JOIN b WHERE b.val > 5 Which one of these you use is mainly a matter of style. The JOIN syntax in the FROM clause is - probably not as portable to other SQL database products. For + probably not as portable to other SQL database management systems. For outer joins there is no choice in any case: they must be done in the FROM clause. An ON/USING clause of an outer join is not equivalent to a @@ -758,7 +758,7 @@ SELECT ... FROM fdt WHERE EXISTS (SELECT c1 FROM t2 WHERE c2 > fdt.c1) - The GROUP BY and HAVING Clauses + The <literal>GROUP BY</literal> and <literal>HAVING</literal> Clauses GROUP BY @@ -1040,7 +1040,7 @@ SELECT a AS value, b + c AS sum FROM ... - DISTINCT + <literal>DISTINCT</literal> DISTINCT @@ -1264,7 +1264,7 @@ SELECT a AS b FROM table1 ORDER BY a; - LIMIT and OFFSET + <literal>LIMIT</literal> and <literal>OFFSET</literal> LIMIT diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index 73ab39cef10..e44d4a35ff2 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -1,5 +1,5 @@ @@ -177,7 +177,7 @@ PostgreSQL documentation Dump data as INSERT commands (rather than COPY). This will make restoration very slow, but it makes the archives more portable to other SQL database - packages. + management systems. diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml index b360c4e457e..00c4d1b9f3e 100644 --- a/doc/src/sgml/ref/pg_dumpall.sgml +++ b/doc/src/sgml/ref/pg_dumpall.sgml @@ -1,5 +1,5 @@ @@ -112,7 +112,7 @@ PostgreSQL documentation Dump data as INSERT commands (rather than COPY). This will make restoration very slow, but it makes the output more portable to other SQL database - packages. + management systems. diff --git a/doc/src/sgml/regress.sgml b/doc/src/sgml/regress.sgml index 693a7583735..8ccd23d1528 100644 --- a/doc/src/sgml/regress.sgml +++ b/doc/src/sgml/regress.sgml @@ -1,4 +1,4 @@ - + Regression Tests @@ -60,7 +60,6 @@ gmake check linkend="regress-evaluation"> below for more. - Because this test method runs a temporary server, it will not work when you are the root user (since the server will not start as root). @@ -82,9 +81,7 @@ gmake check Alternatively, run the tests after installation. - - The parallel regression test starts quite a few processes under your user ID. Presently, the maximum concurrency is twenty parallel test @@ -101,9 +98,7 @@ gmake MAX_CONNECTIONS=10 check runs no more than ten tests concurrently. - - On some systems, the default Bourne-compatible shell (/bin/sh) gets confused when it has to manage @@ -116,7 +111,6 @@ gmake SHELL=/bin/ksh check If no non-broken shell is available, you may be able to work around the problem by limiting the number of connections, as shown above. - To run the tests after installation)]]>, @@ -223,9 +217,9 @@ gmake installcheck - Because USA daylight-saving rules are used, this problem always + Because USA daylight-saving time rules are used, this problem always occurs on the first Sunday of April, the last Sunday of October, - and their following Mondays, regardless of when daylight-saving + and their following Mondays, regardless of when daylight-saving time is in effect where you live. Also note that the problem appears or disappears at midnight Pacific time (UTC-7 or UTC-8), not midnight your local time. Thus the failure may appear late on Saturday or diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 382e1856c58..e6a9478cbb1 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -174,7 +174,7 @@ $ postmaster -D /usr/local/pgsql/data To start the postmaster in the background, use the usual shell syntax: -$ postmaster -D /usr/local/pgsql/data > logfile 2>&1 & +$ postmaster -D /usr/local/pgsql/data >logfile 2>&1 & It is an important to store the server's stdout and stderr output somewhere, as shown above. It will help @@ -344,7 +344,7 @@ FATAL: could not create TCP/IP listen socket A message like FATAL: could not create shared memory segment: Invalid argument -DETAIL: Failed syscall was shmget(key=5440001, size=4011376640, 03600). +DETAIL: Failed system call was shmget(key=5440001, size=4011376640, 03600). probably means your kernel's limit on the size of shared memory is smaller than the work area PostgreSQL @@ -363,7 +363,7 @@ DETAIL: Failed syscall was shmget(key=5440001, size=4011376640, 03600). An error like FATAL: could not create semaphores: No space left on device -DETAIL: Failed syscall was semget(5440126, 17, 03600). +DETAIL: Failed system call was semget(5440126, 17, 03600). does not mean you've run out of disk space. It means your kernel's limit on the number of - - + + commit_delay (integer) @@ -1572,7 +1572,7 @@ SET ENABLE_SEQSCAN TO OFF; Controls which message levels are written to the server log. - Valid values are DEBUG5, DEBUG4, + Valid values are DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, INFO, NOTICE, WARNING, ERROR, LOG, FATAL, and @@ -1591,9 +1591,9 @@ SET ENABLE_SEQSCAN TO OFF; Controls the amount of detail written in the server log for each - message that is logged. Valid values are TERSE, - DEFAULT, and VERBOSE, each adding more - fields to displayed messages. + message that is logged. Valid values are TERSE, + DEFAULT, and VERBOSE, each adding more + fields to displayed messages. @@ -1660,7 +1660,7 @@ SET ENABLE_SEQSCAN TO OFF; Here is a list of the various message severity levels used in - these settings: + these settings: DEBUG[1-5] @@ -2028,9 +2028,9 @@ SET ENABLE_SEQSCAN TO OFF; This parameter is normally true. When set false, it disables - validation of the function body string in CREATE FUNCTION. - Disabling validation is occasionally useful to avoid problems such as - forward references when restoring function definitions from a dump. + validation of the function body string in CREATE FUNCTION. + Disabling validation is occasionally useful to avoid problems such as + forward references when restoring function definitions from a dump. @@ -2100,15 +2100,15 @@ SET ENABLE_SEQSCAN TO OFF; Sets the display format for date and time values, as well as the rules for interpreting ambiguous date input values. - For historical reasons, this variable contains two independent - components: the output format specification (ISO, - Postgres, SQL, or German) and - the date field order specification (DMY, MDY, - or YMD). These can be set separately or together. - The keywords Euro and European are synonyms - for DMY; the keywords US, NonEuro, - and NonEuropean are synonyms for MDY. - See for more information. The + For historical reasons, this variable contains two independent + components: the output format specification (ISO, + Postgres, SQL, or German) and + the date field order specification (DMY, MDY, + or YMD). These can be set separately or together. + The keywords Euro and European are synonyms + for DMY; the keywords US, NonEuro, + and NonEuropean are synonyms for MDY. + See for more information. The default is ISO, MDY. @@ -2390,13 +2390,13 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir' When true, tables that are referenced by a query will be - automatically added to the FROM clause if not already - present. The default is true for compatibility with - previous releases of PostgreSQL. However, this - behavior is not SQL-standard, and many people dislike it because it - can mask mistakes. Set to false for the SQL-standard - behavior of rejecting references to tables that are not listed in - FROM. + automatically added to the FROM clause if not already + present. The default is true for compatibility with + previous releases of PostgreSQL. However, this + behavior is not SQL-standard, and many people dislike it because it + can mask mistakes. Set to false for the SQL-standard + behavior of rejecting references to tables that are not listed in + FROM. @@ -2521,10 +2521,10 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir' If nonzero, a delay of this many seconds occurs just after a new - server process is forked, before it conducts the authentication - process. This is intended to give an opportunity to attach to the - server process with a debugger to trace down misbehavior in - authentication. + server process is forked, before it conducts the authentication + process. This is intended to give an opportunity to attach to the + server process with a debugger to trace down misbehavior in + authentication. @@ -2993,9 +2993,10 @@ options SEMMAP=256 option singular.) - You might also want to use the sysctl setting to - lock shared memory into RAM and prevent it from being paged out - to swap, e.g. kern.ipc.shm_use_phys. + You might also want to configure your kernel to lock shared + memory into RAM and prevent it from being paged out to swap. + Use the sysctl setting + kern.ipc.shm_use_phys. @@ -3059,65 +3060,6 @@ kernel.shmmax = 134217728 /usr/src/linux/include/asm-xxx/shmpara m.h and /usr/src/linux/include/linux/sem.h. - - - Linux kernel version 2.4.* has poor default memory overcommit - behavior, which can result in the postmaster being killed by the - kernel due to memory demands by another process if the system - runs out of memory. - - - - The symptom of this occurring is a kernel message looking like - this (consult your system documentation and configuration on - where to look for such a message): - - Out of Memory: Killed process 12345 (postmaster). - - - - - To avoid this situation, run PostgreSQL - on a machine where you - can be sure that other processes will not run the machine out - of memory. If your kernel supports strict and/or paranoid modes - of overcommit handling, you can also relieve this problem by - altering the system's default behaviour. This can be determined - by examining the function vm_enough_memory - in the file mm/mmap.c in the kernel source. - If this file reveals that strict and/or paranoid modes are - supported by your kernel, turn one of these modes on by using - -sysctl -w vm.overcommit_memory=2 - - for strict mode or - -sysctl -w vm.overcommit_memory=3 - - for paranoid mode, or placing an equivalent entry in - /etc/sysctl.conf. - - - - - Warning: using these settings in a kernel which does not support - these modes will almost certainly increase the danger of the - kernel killing the postmaster, rather than reducing it. - If in any doubt, consult a kernel expert or your kernel vendor. - - - - - These modes are expected to be supported in all 2.6 and later - kernels. Some vendor 2.4 kernels may also support these modes. - However, it is known that some vendor documents suggest that - they support them while examination of the kernel source reveals - that they do not. - - - - Note, you will need enough swap space to cover all your memory needs. - @@ -3319,6 +3261,71 @@ default:\ + + Linux Memory Overcommit + + + Linux kernels of version 2.4.* have a poor default memory + overcommit behavior, which can result in the PostgreSQL server + (postmaster process) being killed by the + kernel if the memory demands of another process cause the system + to run out of memory. + + + + If this happens, you will see a kernel message looking like this + (consult your system documentation and configuration on where to + look for such a message): + +Out of Memory: Killed process 12345 (postmaster). + + And, of course, you will find that your database server has + disappeared. + + + + To avoid this situation, run PostgreSQL + on a machine where you can be sure that other processes will not + run the machine out of memory. If your kernel supports the strict + and/or paranoid modes of overcommit handling, you can also relieve + this problem by altering the system's default behaviour. This can + be determined by examining the function + vm_enough_memory in the file mm/mmap.c + in the kernel source. If this file reveals that the strict and/or + paranoid modes are supported by your kernel, turn one of these + modes on by using + +sysctl -w vm.overcommit_memory=2 + + for strict mode, or + +sysctl -w vm.overcommit_memory=3 + + for paranoid mode, or placing an equivalent entry in + /etc/sysctl.conf. + + + + + Using these settings in a kernel which does not support these + modes will almost certainly increase the danger of the kernel + killing the database server, rather than reducing it. If in any + doubt, consult a kernel expert or your kernel vendor. + + + + + These modes are expected to be supported in all 2.6 and later + kernels. Some vendor 2.4 kernels may also support these modes. It + is, however, known that some vendor documents suggest that they + support them while examination of the kernel source reveals that + they do not. + + + + Note, you will need enough swap space to cover all your memory needs. + + diff --git a/doc/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml index 0a31d1127c4..dc77f0abc65 100644 --- a/doc/src/sgml/syntax.sgml +++ b/doc/src/sgml/syntax.sgml @@ -1,5 +1,5 @@ @@ -196,20 +196,16 @@ UPDATE "my_table" SET "a" = 5; unquoted names are always folded to lower case. For example, the identifiers FOO, foo, and "foo" are considered the same by - PostgreSQL, but "Foo" - and "FOO" are different from these three and - each other. - - - The folding of unquoted names to lower case in PostgreSQL - is incompatible with the SQL standard, which says that unquoted - names should be folded to upper case. Thus, foo - should be equivalent to "FOO" not - "foo" according to the standard. If you want to - write portable applications you are advised to always quote a particular - name or never quote it. - - + PostgreSQL, but + "Foo" and "FOO" are + different from these three and each other. (The folding of + unquoted names to lower case in PostgreSQL is + incompatible with the SQL standard, which says that unquoted names + should be folded to upper case. Thus, foo + should be equivalent to "FOO" not + "foo" according to the standard. If you want + to write portable applications you are advised to always quote a + particular name or never quote it. @@ -260,10 +256,12 @@ UPDATE "my_table" SET "a" = 5; form feed, \n is a newline, \r is a carriage return, \t is a tab, and \xxx, - where xxx is an octal number, is the - character with the corresponding ASCII code. Any other character - following a backslash is taken literally. Thus, to include a - backslash in a string constant, type two backslashes. + where xxx is an octal number, is a + byte with the corresponding code. (It is your responsibility + that the byte sequences you create are valid characters in the + server character set encoding.) Any other character following a + backslash is taken literally. Thus, to include a backslash in a + string constant, type two backslashes. @@ -440,44 +438,8 @@ CAST ( 'string' AS type ) or CAST() to specify the type of an array constant. - - - Array constants - - - array - constant - - - - The general format of an array constant is the following: - -'{ val1 delim val2 delim ... }' - - where delim is the delimiter character - for the type, as recorded in its pg_type - entry. (For all built-in types, this is the comma character - ,.) Each val is either a constant - of the array element type, or a subarray. An example of an - array constant is - -'{{1,2,3},{4,5,6},{7,8,9}}' - - This constant is a two-dimensional, 3-by-3 array consisting of three - subarrays of integers. For more information see . - - - - (Array constants are actually only a special case of the generic - type constants discussed in the previous section. The constant - is initially treated as a string and passed to the array input - conversion routine. An explicit type specification might be - necessary.) - - - Operators @@ -622,7 +584,7 @@ CAST ( 'string' AS type ) A comment is an arbitrary sequence of characters beginning with double dashes and extending to the end of the line, e.g.: --- This is a standard SQL92 comment +-- This is a standard SQL comment @@ -635,7 +597,7 @@ CAST ( 'string' AS type ) where the comment begins with /* and extends to the matching occurrence of */. These block - comments nest, as specified in SQL99 but unlike C, so that one can + comments nest, as specified in the SQL standard but unlike C, so that one can comment out larger blocks of code that may contain existing block comments. @@ -1267,7 +1229,7 @@ CAST ( expression AS type there is no error; the scalar result is taken to be null.) The subquery can refer to variables from the surrounding query, which will act as constants during any one evaluation of the subquery. - See also . + See also for other expressions involving subqueries. @@ -1289,7 +1251,7 @@ SELECT name, (SELECT max(pop) FROM cities WHERE cities.state = states.name) - An array constructor is an expression that builds an + An array constructor is an expression that builds an array value from values for its member elements. A simple array constructor consists of the key word ARRAY, a left square bracket @@ -1337,11 +1299,11 @@ SELECT ARRAY[[1,2],[3,4]]; an array of the proper kind, not only a sub-ARRAY construct. For example: -create table arr(f1 int[], f2 int[]); -CREATE TABLE -insert into arr values (ARRAY[[1,2],[3,4]],ARRAY[[5,6],[7,8]]); -INSERT 2635544 1 -select ARRAY[f1, f2, '{{9,10},{11,12}}'::int[]] from arr; +CREATE TABLE arr(f1 int[], f2 int[]); + +INSERT INTO arr VALUES (ARRAY[[1,2],[3,4]], ARRAY[[5,6],[7,8]]); + +SELECT ARRAY[f1, f2, '{{9,10},{11,12}}'::int[]] FROM arr; array ------------------------------------------------ {{{1,2},{3,4}},{{5,6},{7,8}},{{9,10},{11,12}}} @@ -1361,10 +1323,10 @@ SELECT ARRAY(SELECT oid FROM pg_proc WHERE proname LIKE 'bytea%'); {2011,1954,1948,1952,1951,1244,1950,2005,1949,1953,2006,31} (1 row) - The subquery must return a single column. The - resulting one-dimensional array will have an element for each row in the - subquery result, with an element type matching that of the subquery's - output column. + The subquery must return a single column. The resulting + one-dimensional array will have an element for each row in the + subquery result, with an element type matching that of the + subquery's output column. diff --git a/doc/src/sgml/typeconv.sgml b/doc/src/sgml/typeconv.sgml index d98bb7d968f..a0dd5cf0329 100644 --- a/doc/src/sgml/typeconv.sgml +++ b/doc/src/sgml/typeconv.sgml @@ -1,5 +1,5 @@ @@ -794,13 +794,14 @@ padding spaces. -SQL UNION constructs must match up possibly dissimilar types to -become a single result set. The resolution algorithm is applied separately -to each output column of a union query. The INTERSECT and -EXCEPT constructs resolve dissimilar types in the same way as -UNION. -A CASE construct uses the identical algorithm to match up its -component expressions and select a result data type, as does ARRAY. +SQL UNION constructs must match up possibly dissimilar +types to become a single result set. The resolution algorithm is +applied separately to each output column of a union query. The +INTERSECT and EXCEPT constructs resolve +dissimilar types in the same way as UNION. The +CASE and ARRAY constructs use the identical +algorithm to match up their component expressions and select a result +data type.