From: Tom Lane Date: Tue, 1 Nov 2005 21:09:51 +0000 (+0000) Subject: Make an editorial pass over the reference pages. X-Git-Url: http://waps.l3s.uni-hannover.de/gitweb/?a=commitdiff_plain;h=bd20d972c88b95350000a97d7e44d18a39142ea4;p=users%2Fbernd%2Fpostgres.git Make an editorial pass over the reference pages. --- diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml index 38ad681af0..add498c32e 100644 --- a/doc/src/sgml/maintenance.sgml +++ b/doc/src/sgml/maintenance.sgml @@ -586,7 +586,8 @@ analyze threshold = analyze base threshold + analyze scale factor * number of tu In some situations it is worthwhile to rebuild indexes periodically - with the REINDEX command. + with the + command. diff --git a/doc/src/sgml/ref/alter_domain.sgml b/doc/src/sgml/ref/alter_domain.sgml index 23b954abe9..d5e919d079 100644 --- a/doc/src/sgml/ref/alter_domain.sgml +++ b/doc/src/sgml/ref/alter_domain.sgml @@ -237,7 +237,8 @@ ALTER DOMAIN zipcode SET SCHEMA customers; Compatibility - ALTER DOMAIN conforms with SQL:2003, + ALTER DOMAIN conforms to the SQL + standard, except for the OWNER and SET SCHEMA variants, which are PostgreSQL extensions. diff --git a/doc/src/sgml/ref/alter_function.sgml b/doc/src/sgml/ref/alter_function.sgml index 6d65f03475..fb9695ddd5 100644 --- a/doc/src/sgml/ref/alter_function.sgml +++ b/doc/src/sgml/ref/alter_function.sgml @@ -149,8 +149,9 @@ where action is one of: CALLED ON NULL INPUT changes the function so that it will be invoked when some or all of its arguments are null. RETURNS NULL ON NULL INPUT or - STRICT changes the function so that it - always returns null if any of its arguments are null. See STRICT changes the function so that it is not + invoked if any of its arguments are null; instead, a null result + is assumed automatically. See for more information. @@ -164,8 +165,7 @@ where action is one of: Change the volatility of the function to the specified - type. See for more - information about function volatility. + setting. See for details. @@ -233,7 +233,7 @@ ALTER FUNCTION sqrt(integer) SET SCHEMA maths; properties of a function to be modified, but does not provide the ability to rename a function, make a function a security definer, or change the owner, schema, or volatility of a function. The standard also - requires the RESTRICT key word; it is optional in + requires the RESTRICT key word, which is optional in PostgreSQL. diff --git a/doc/src/sgml/ref/alter_sequence.sgml b/doc/src/sgml/ref/alter_sequence.sgml index 4d6c7a67a9..cdd89787a2 100644 --- a/doc/src/sgml/ref/alter_sequence.sgml +++ b/doc/src/sgml/ref/alter_sequence.sgml @@ -215,7 +215,8 @@ ALTER SEQUENCE serial RESTART WITH 105; Compatibility - ALTER SEQUENCE conforms with SQL:2003, + ALTER SEQUENCE conforms to the SQL + standard, except for the SET SCHEMA variant, which is a PostgreSQL extension. diff --git a/doc/src/sgml/ref/create_cast.sgml b/doc/src/sgml/ref/create_cast.sgml index d3f89fddd7..7e89d5c1db 100644 --- a/doc/src/sgml/ref/create_cast.sgml +++ b/doc/src/sgml/ref/create_cast.sgml @@ -298,8 +298,9 @@ CREATE CAST (text AS int4) WITH FUNCTION int4(text); Compatibility - The CREATE CAST command conforms to SQL:2003, - except that SQL:2003 does not make provisions for binary-compatible + The CREATE CAST command conforms to the + SQL standard, + except that SQL does not make provisions for binary-compatible types or extra arguments to implementation functions. AS IMPLICIT is a PostgreSQL extension, too. diff --git a/doc/src/sgml/ref/create_domain.sgml b/doc/src/sgml/ref/create_domain.sgml index 4d13938752..654754b685 100644 --- a/doc/src/sgml/ref/create_domain.sgml +++ b/doc/src/sgml/ref/create_domain.sgml @@ -55,13 +55,17 @@ where constraint is: constraints individually. - + - Keep in mind also that declaring a function result value as a domain + At present, declaring a function result value as a domain is pretty dangerous, because none of the PLs enforce domain constraints - on their results. + on their results. You'll need to make sure that the function code itself + respects the constraints. In PL/pgSQL, one possible + workaround is to explicitly cast the result value to the domain type + when you return it. PL/pgSQL does not enforce domain + constraints for local variables within functions, either. - + diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml index 0a2cab49ad..e3b398fc76 100644 --- a/doc/src/sgml/ref/create_function.sgml +++ b/doc/src/sgml/ref/create_function.sgml @@ -228,9 +228,9 @@ CREATE [ OR REPLACE ] FUNCTION change even within a single table scan, so no optimizations can be made. Relatively few database functions are volatile in this sense; some examples are random(), currval(), - timeofday(). Note that any function that has side-effects - must be classified volatile, even if its result is quite predictable, - to prevent calls from being optimized away; an example is + timeofday(). But note that any function that has + side-effects must be classified volatile, even if its result is quite + predictable, to prevent calls from being optimized away; an example is setval(). @@ -279,9 +279,9 @@ CREATE [ OR REPLACE ] FUNCTION - The key word EXTERNAL is present for SQL - conformance but is optional since, unlike in SQL, this feature - does not only apply to external functions. + The key word EXTERNAL is allowed for SQL + conformance, but it is optional since, unlike in SQL, this feature + applies to all functions not only external ones. @@ -478,7 +478,7 @@ SELECT * FROM dup(42); Compatibility - A CREATE FUNCTION command is defined in SQL:2003. + A CREATE FUNCTION command is defined in SQL:1999 and later. The PostgreSQL version is similar but not fully compatible. The attributes are not portable, neither are the different available languages. diff --git a/doc/src/sgml/ref/create_sequence.sgml b/doc/src/sgml/ref/create_sequence.sgml index 440c3648a9..19b036a862 100644 --- a/doc/src/sgml/ref/create_sequence.sgml +++ b/doc/src/sgml/ref/create_sequence.sgml @@ -297,8 +297,8 @@ END; Compatibility - CREATE SEQUENCE is is specified in SQL:2003. - PostgreSQL conforms with the standard, with the following exceptions: + CREATE SEQUENCE conforms to the SQL + standard, with the following exceptions: The standard's AS <data type> expression is not supported. Obtaining the next value is done using the nextval() function instead of the standard's NEXT VALUE FOR expression. diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 0af0b42c5d..f60ebf4d58 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -20,11 +20,12 @@ PostgreSQL documentation -CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE table_name ( - [ column_name data_type [ DEFAULT default_expr ] [ column_constraint [ ... ] ] +CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE table_name ( [ + { column_name data_type [ DEFAULT default_expr ] [ column_constraint [ ... ] ] | table_constraint - | LIKE parent_table [ { INCLUDING | EXCLUDING } DEFAULTS ] ] [, ... ] -) + | LIKE parent_table [ { INCLUDING | EXCLUDING } DEFAULTS ] } + [, ... ] +] ) [ INHERITS ( parent_table [, ... ] ) ] [ WITH OIDS | WITHOUT OIDS ] [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ] @@ -861,8 +862,8 @@ CREATE TABLE cinemas ( Compatibility - The CREATE TABLE command conforms to SQL-92 and - to a subset of SQL:2003, with exceptions listed below. + The CREATE TABLE command conforms to the + SQL standard, with exceptions listed below. @@ -940,8 +941,8 @@ CREATE TABLE cinemas ( Multiple inheritance via the INHERITS clause is a PostgreSQL language extension. - SQL:2003 defines single inheritance using a - different syntax and different semantics. SQL:2003-style + SQL:1999 and later define single inheritance using a + different syntax and different semantics. SQL:1999-style inheritance is not yet supported by PostgreSQL. diff --git a/doc/src/sgml/ref/create_table_as.sgml b/doc/src/sgml/ref/create_table_as.sgml index 6da2b9b60c..745eff13f9 100644 --- a/doc/src/sgml/ref/create_table_as.sgml +++ b/doc/src/sgml/ref/create_table_as.sgml @@ -20,7 +20,8 @@ PostgreSQL documentation -CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE table_name [ (column_name [, ...] ) ] [ [ WITH | WITHOUT ] OIDS ] +CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE table_name + [ (column_name [, ...] ) ] [ [ WITH | WITHOUT ] OIDS ] AS query @@ -143,17 +144,17 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE table_name Prior to PostgreSQL 8.0, CREATE TABLE AS always included OIDs in the table it - produced. As of PostgreSQL 8.0, + created. As of PostgreSQL 8.0, the CREATE TABLE AS command allows the user to explicitly specify whether OIDs should be included. If the presence of OIDs is not explicitly specified, the configuration variable is - used. While this variable currently defaults to true, the default - value may be changed in the future. Therefore, applications that + used. As of PostgreSQL 8.1, + this variable is false by default, so the default behavior is not + identical to pre-8.0 releases. Applications that require OIDs in the table created by CREATE TABLE - AS should explicitly specify WITH - OIDS to ensure compatibility with future versions - of PostgreSQL. + AS should explicitly specify WITH OIDS + to ensure proper behavior. @@ -175,10 +176,8 @@ CREATE TABLE films_recent AS Compatibility - CREATE TABLE AS is specified by the SQL:2003 - standard. There are some small differences between the definition - of the command in SQL:2003 and its implementation in - PostgreSQL: + CREATE TABLE AS conforms to the SQL + standard, with the following exceptions: @@ -198,8 +197,26 @@ CREATE TABLE films_recent AS - The standard defines a WITH DATA clause; + The standard defines a WITH [ NO ] DATA clause; this is not currently implemented by PostgreSQL. + The behavior provided by PostgreSQL is equivalent + to the standard's WITH DATA case. + + + + + + WITH/WITHOUT OIDS is a PostgreSQL + extension. + + + + + + PostgreSQL handles temporary tables in a way + rather different from the standard; see + + for details. diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml index 4d5ef99911..55454cc404 100644 --- a/doc/src/sgml/ref/create_trigger.sgml +++ b/doc/src/sgml/ref/create_trigger.sgml @@ -208,19 +208,19 @@ CREATE TRIGGER name { BEFORE | AFTE The CREATE TRIGGER statement in PostgreSQL implements a subset of the - SQL:2003 standard. The following functionality is currently missing: + SQL standard. The following functionality is currently missing: - SQL:2003 allows triggers to fire on updates to specific columns + SQL allows triggers to fire on updates to specific columns (e.g., AFTER UPDATE OF col1, col2). - SQL:2003 allows you to define aliases for the old + SQL allows you to define aliases for the old and new rows or tables for use in the definition of the triggered action (e.g., CREATE TRIGGER ... ON tablename REFERENCING OLD ROW AS somename NEW ROW AS othername @@ -234,9 +234,9 @@ CREATE TRIGGER name { BEFORE | AFTE PostgreSQL only allows the execution - of a user-defined function for the triggered action. SQL:2003 + of a user-defined function for the triggered action. The standard allows the execution of a number of other SQL commands, such as - CREATE TABLE as triggered action. This + CREATE TABLE as the triggered action. This limitation is not hard to work around by creating a user-defined function that executes the desired commands. @@ -245,7 +245,7 @@ CREATE TRIGGER name { BEFORE | AFTE - SQL:2003 specifies that multiple triggers should be fired in + SQL specifies that multiple triggers should be fired in time-of-creation order. PostgreSQL uses name order, which was judged more convenient to work with. diff --git a/doc/src/sgml/ref/create_type.sgml b/doc/src/sgml/ref/create_type.sgml index 79a8783736..8844c2b0cd 100644 --- a/doc/src/sgml/ref/create_type.sgml +++ b/doc/src/sgml/ref/create_type.sgml @@ -533,8 +533,8 @@ CREATE TABLE big_objs ( This CREATE TYPE command is a PostgreSQL extension. There is a - CREATE TYPE statement in SQL:2003 that is rather - different in detail. + CREATE TYPE statement in the SQL standard + that is rather different in detail. diff --git a/doc/src/sgml/ref/create_view.sgml b/doc/src/sgml/ref/create_view.sgml index f0d643daed..dc6ffc500f 100644 --- a/doc/src/sgml/ref/create_view.sgml +++ b/doc/src/sgml/ref/create_view.sgml @@ -20,8 +20,8 @@ PostgreSQL documentation -CREATE [ OR REPLACE ] [ TEMP | TEMPORARY ] VIEW name [ ( column_name [, ...] ) ] AS query +CREATE [ OR REPLACE ] [ TEMP | TEMPORARY ] VIEW name [ ( column_name [, ...] ) ] + AS query @@ -62,16 +62,14 @@ class="PARAMETER">column_name [, ...] ) ] AS name [ ( column [, ...] ) ] - AS query +CREATE VIEW name [ ( column_name [, ...] ) ] + AS query [ WITH [ CASCADED | LOCAL ] CHECK OPTION ] @@ -224,6 +222,7 @@ CREATE VIEW name [ ( CREATE OR REPLACE VIEW is a PostgreSQL language extension. + So is the concept of a temporary view. diff --git a/doc/src/sgml/ref/createuser.sgml b/doc/src/sgml/ref/createuser.sgml index 06b9c8765e..bf8d467f7b 100644 --- a/doc/src/sgml/ref/createuser.sgml +++ b/doc/src/sgml/ref/createuser.sgml @@ -92,6 +92,7 @@ PostgreSQL documentation The new user will not be a superuser. + This is the default. @@ -112,6 +113,7 @@ PostgreSQL documentation The new user will not be allowed to create databases. + This is the default. @@ -133,6 +135,7 @@ PostgreSQL documentation The new user will not be allowed to create new roles. + This is the default. diff --git a/doc/src/sgml/ref/delete.sgml b/doc/src/sgml/ref/delete.sgml index cf11e6b3d5..adc2c63e31 100644 --- a/doc/src/sgml/ref/delete.sgml +++ b/doc/src/sgml/ref/delete.sgml @@ -46,7 +46,7 @@ DELETE FROM [ ONLY ] table By default, DELETE will delete rows in the - specified table and all its subtables. If you wish to delete only + specified table and all its child tables. If you wish to delete only from the specific table mentioned, you must use the ONLY clause. @@ -72,6 +72,16 @@ DELETE FROM [ ONLY ] table Parameters + + ONLY + + + If specified, delete rows from the named table only. When not + specified, any tables inheriting from the named table are also processed. + + + + table @@ -90,7 +100,9 @@ DELETE FROM [ ONLY ] table to the list of tables that can be specified in the of a SELECT statement; for example, an alias for - the table name can be specified. + the table name can be specified. Do not repeat the target table + in the usinglist, + unless you wish to set up a self-join. @@ -99,8 +111,8 @@ DELETE FROM [ ONLY ] table condition - A value expression that returns a value of type - boolean that determines the rows which are to be + An expression returning a value of type + boolean, which determines the rows that are to be deleted. diff --git a/doc/src/sgml/ref/drop_sequence.sgml b/doc/src/sgml/ref/drop_sequence.sgml index b3ede4ff65..f913270c22 100644 --- a/doc/src/sgml/ref/drop_sequence.sgml +++ b/doc/src/sgml/ref/drop_sequence.sgml @@ -82,8 +82,8 @@ DROP SEQUENCE serial; Compatibility - DROP SEQUENCE conforms with - SQL:2003, except that the standard only allows one + DROP SEQUENCE conforms to the SQL + standard, except that the standard only allows one sequence to be dropped per command. diff --git a/doc/src/sgml/ref/pg_config-ref.sgml b/doc/src/sgml/ref/pg_config-ref.sgml index 1c2dd2a474..9c969d6c9b 100644 --- a/doc/src/sgml/ref/pg_config-ref.sgml +++ b/doc/src/sgml/ref/pg_config-ref.sgml @@ -277,7 +277,10 @@ - The options , , + The options , , + , , + , , + , , , , , , and are new in PostgreSQL 8.1. diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index 68c60cbdbc..b2c6f6b301 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -194,18 +194,19 @@ PostgreSQL documentation - - - - - - Create the dump in the specified encoding. By default, the dump is - created in the database encoding. - - + + + + + + Create the dump in the specified character set encoding. By default, + the dump is created in the database encoding. (Another way to get the + same result is to set the PGCLIENTENCODING environment + variable to the desired dump encoding.) + + - @@ -474,10 +475,13 @@ PostgreSQL documentation - Output SQL standard SET SESSION AUTHORIZATION commands instead of - ALTER OWNER commands. This makes the dump more standards compatible, - but depending on the history of the objects in the dump, may not - restore properly. + Output SQL-standard SET SESSION AUTHORIZATION commands + instead of ALTER OWNER commands to determine object + ownership. This makes the dump more standards compatible, but + depending on the history of the objects in the dump, may not restore + properly. Also, a dump using SET SESSION AUTHORIZATION + will certainly require superuser privileges to restore correctly, + whereas ALTER OWNER requires lesser privileges. diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml index 9408dc2d80..4fa417d3fb 100644 --- a/doc/src/sgml/ref/pg_dumpall.sgml +++ b/doc/src/sgml/ref/pg_dumpall.sgml @@ -278,10 +278,11 @@ PostgreSQL documentation - Output SQL standard SET SESSION AUTHORIZATION commands instead of - ALTER OWNER commands. This makes the dump more standards compatible, - but depending on the history of the objects in the dump, may not - restore properly. + Output SQL-standard SET SESSION AUTHORIZATION commands + instead of ALTER OWNER commands to determine object + ownership. This makes the dump more standards compatible, but + depending on the history of the objects in the dump, may not restore + properly. diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index aeab304699..7497e149df 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -243,9 +243,9 @@ - Restore only definitions and/or data in the named schema. Not to be - confused with the option. This can be combined with - option. + Restore only objects that are in the named schema. This can be + combined with the option to restore just a + specific table. @@ -298,8 +298,10 @@ - Restore only the schema (data definitions), not the data. - Sequence values will be reset. + Restore only the schema (data definitions), not the data (table + contents). Sequence current values will not be restored, either. + (Do not confuse this with the @@ -361,10 +363,11 @@ - Output SQL standard SET SESSION AUTHORIZATION - commands instead of ALTER OWNER commands. This - makes the dump more standards compatible, but depending on the - history of the objects in the dump, may not restore properly. + Output SQL-standard SET SESSION AUTHORIZATION commands + instead of ALTER OWNER commands to determine object + ownership. This makes the dump more standards compatible, but + depending on the history of the objects in the dump, may not restore + properly. diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index 77f3eb64e6..390c98b76f 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -227,8 +227,9 @@ PostgreSQL documentation - Write all query output into file filename in addition to the regular output source. + Write all query output into file filename, in addition to the + normal output destination. @@ -601,7 +602,7 @@ testdb=> precede it by a backslash. Anything contained in single quotes is furthermore subject to C-like substitutions for \n (new line), \t (tab), - \digits (octal), + \digits (octal), and \xdigits (hexadecimal). @@ -2015,12 +2016,13 @@ bar The filename that will be used to store the history list. The default - value is ~/.psql_history. For example, using: + value is ~/.psql_history. For example, putting \set HISTFILE ~/.psql_history- :DBNAME - in ~/.psqlrc will get psql to - maintain a separate history for each database. + in ~/.psqlrc will cause + psql to maintain a separate history for + each database. diff --git a/doc/src/sgml/ref/release_savepoint.sgml b/doc/src/sgml/ref/release_savepoint.sgml index 95008cb1ef..ffd7c76f63 100644 --- a/doc/src/sgml/ref/release_savepoint.sgml +++ b/doc/src/sgml/ref/release_savepoint.sgml @@ -108,7 +108,7 @@ COMMIT; Compatibility - This command conforms to the SQL:2003 standard. The standard + This command conforms to the SQL standard. The standard specifies that the key word SAVEPOINT is mandatory, but PostgreSQL allows it to be omitted. diff --git a/doc/src/sgml/ref/rollback_to.sgml b/doc/src/sgml/ref/rollback_to.sgml index 7c60da5448..5f474420c7 100644 --- a/doc/src/sgml/ref/rollback_to.sgml +++ b/doc/src/sgml/ref/rollback_to.sgml @@ -130,11 +130,11 @@ COMMIT; Compatibility - The SQL:2003 standard specifies that the key word + The SQL standard specifies that the key word SAVEPOINT is mandatory, but PostgreSQL - and Oracle allow it to be omitted. SQL:2003 allows + and Oracle allow it to be omitted. SQL allows only WORK, not TRANSACTION, as a noise word - after ROLLBACK. Also, SQL:2003 has an optional clause + after ROLLBACK. Also, SQL has an optional clause AND [ NO ] CHAIN which is not currently supported by PostgreSQL. Otherwise, this command conforms to the SQL standard. diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml index 7d882614db..c5c44fe120 100644 --- a/doc/src/sgml/ref/select.sgml +++ b/doc/src/sgml/ref/select.sgml @@ -1095,7 +1095,7 @@ SELECT distributors.* WHERE distributors.name = 'Westward'; Namespace Available to <literal>GROUP BY</literal> and <literal>ORDER BY</literal> - In the SQL:2003 standard, an ORDER BY clause may + In the SQL-92 standard, an ORDER BY clause may only use result column names or numbers, while a GROUP BY clause may only use expressions based on input column names. PostgreSQL extends each of @@ -1108,11 +1108,11 @@ SELECT distributors.* WHERE distributors.name = 'Westward'; - SQL:2003 uses a slightly different definition which is not entirely upward - compatible with SQL-92. + SQL:1999 and later use a slightly different definition which is not + entirely upward compatible with SQL-92. In most cases, however, PostgreSQL will interpret an ORDER BY or GROUP - BY expression the same way SQL:2003 does. + BY expression the same way SQL:1999 does. diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml index 76ca860b94..5eb4c4bf6f 100644 --- a/doc/src/sgml/ref/vacuum.sgml +++ b/doc/src/sgml/ref/vacuum.sgml @@ -176,12 +176,10 @@ VACUUM [ FULL | FREEZE ] [ VERBOSE ] ANALYZE [ ta - During VACUUM execution, there can be a substantial - increase in I/O traffic, which cause poor performance for other active - sessions. Therefore, it is sometimes advisable to use - the cost-based vacuum delay feature. See for more - details. + VACUUM causes a substantial increase in I/O traffic, + which can cause poor performance for other active sessions. Therefore, + it is sometimes advisable to use the cost-based vacuum delay feature. + See for details. @@ -238,7 +236,7 @@ VACUUM - + diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 5973526ad6..54cf69cfec 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1773,21 +1773,25 @@ psql -t -f fixseq.sql db1 | psql -e db1 pg_restore (Richard van den Berg) - This allows only objects from a specified schema to be restored. + This allows just the objects in a specified schema to be restored. - Allow pg_dump to dump a consistent snapshot of - large objects (Tom) + Allow pg_dump to dump large objects even in + text mode (Tom) + + + With this change, large objects are now always dumped; the former + - Allow pg_dump to dump large objects even in - text mode (Tom) + Allow pg_dump to dump a consistent snapshot of + large objects (Tom)