From 03a321d2143cd1168d10960cada9d688c5140520 Mon Sep 17 00:00:00 2001 From: "Thomas G. Lockhart" Date: Sat, 8 Dec 2001 03:24:40 +0000 Subject: Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL. --- doc/src/sgml/ref/abort.sgml | 6 +++--- doc/src/sgml/ref/allfiles.sgml | 4 ++-- doc/src/sgml/ref/alter_group.sgml | 4 ++-- doc/src/sgml/ref/alter_table.sgml | 8 ++++---- doc/src/sgml/ref/alter_user.sgml | 6 +++--- doc/src/sgml/ref/analyze.sgml | 6 +++--- doc/src/sgml/ref/begin.sgml | 12 ++++++------ doc/src/sgml/ref/close.sgml | 6 +++--- doc/src/sgml/ref/cluster.sgml | 10 +++++----- doc/src/sgml/ref/comment.sgml | 4 ++-- doc/src/sgml/ref/commit.sgml | 4 ++-- doc/src/sgml/ref/copy.sgml | 16 +++++++++------- doc/src/sgml/ref/create_aggregate.sgml | 10 +++++----- doc/src/sgml/ref/create_constraint.sgml | 4 ++-- doc/src/sgml/ref/create_database.sgml | 22 +++++++++++++++------- doc/src/sgml/ref/create_function.sgml | 6 +++--- doc/src/sgml/ref/create_group.sgml | 6 +++--- doc/src/sgml/ref/create_index.sgml | 19 ++++++++++--------- doc/src/sgml/ref/create_language.sgml | 4 ++-- doc/src/sgml/ref/create_operator.sgml | 27 ++++++++++++++------------- doc/src/sgml/ref/create_rule.sgml | 14 +++++++------- doc/src/sgml/ref/create_sequence.sgml | 6 +++--- doc/src/sgml/ref/create_table.sgml | 7 ++++--- doc/src/sgml/ref/create_table_as.sgml | 4 ++-- doc/src/sgml/ref/create_trigger.sgml | 4 ++-- doc/src/sgml/ref/create_type.sgml | 4 ++-- doc/src/sgml/ref/create_user.sgml | 10 +++++----- doc/src/sgml/ref/create_view.sgml | 4 ++-- doc/src/sgml/ref/createdb.sgml | 4 ++-- doc/src/sgml/ref/createlang.sgml | 4 ++-- doc/src/sgml/ref/createuser.sgml | 4 ++-- doc/src/sgml/ref/current_time.sgml | 4 ++-- doc/src/sgml/ref/current_timestamp.sgml | 4 ++-- doc/src/sgml/ref/current_user.sgml | 4 ++-- doc/src/sgml/ref/declare.sgml | 28 ++++++++++++++-------------- doc/src/sgml/ref/delete.sgml | 8 ++++---- doc/src/sgml/ref/drop_aggregate.sgml | 6 +++--- doc/src/sgml/ref/drop_database.sgml | 6 +++--- doc/src/sgml/ref/drop_function.sgml | 4 ++-- doc/src/sgml/ref/drop_group.sgml | 4 ++-- doc/src/sgml/ref/drop_index.sgml | 6 +++--- doc/src/sgml/ref/drop_language.sgml | 6 +++--- doc/src/sgml/ref/drop_operator.sgml | 6 +++--- doc/src/sgml/ref/drop_rule.sgml | 10 +++++----- doc/src/sgml/ref/drop_sequence.sgml | 6 +++--- doc/src/sgml/ref/drop_table.sgml | 4 ++-- doc/src/sgml/ref/drop_trigger.sgml | 4 ++-- doc/src/sgml/ref/drop_type.sgml | 4 ++-- doc/src/sgml/ref/drop_user.sgml | 6 +++--- doc/src/sgml/ref/drop_view.sgml | 6 +++--- doc/src/sgml/ref/dropdb.sgml | 4 ++-- doc/src/sgml/ref/droplang.sgml | 4 ++-- doc/src/sgml/ref/dropuser.sgml | 4 ++-- doc/src/sgml/ref/ecpg-ref.sgml | 4 ++-- doc/src/sgml/ref/end.sgml | 6 +++--- doc/src/sgml/ref/explain.sgml | 17 ++++++++++------- doc/src/sgml/ref/fetch.sgml | 18 +++++++++--------- doc/src/sgml/ref/grant.sgml | 6 +++--- doc/src/sgml/ref/initdb.sgml | 4 ++-- doc/src/sgml/ref/initlocation.sgml | 6 +++--- doc/src/sgml/ref/insert.sgml | 6 +++--- doc/src/sgml/ref/ipcclean.sgml | 4 ++-- doc/src/sgml/ref/listen.sgml | 10 +++++----- doc/src/sgml/ref/lock.sgml | 12 ++++++------ doc/src/sgml/ref/move.sgml | 6 +++--- doc/src/sgml/ref/notify.sgml | 14 +++++++------- doc/src/sgml/ref/pg_ctl-ref.sgml | 4 ++-- doc/src/sgml/ref/pg_dump.sgml | 8 ++++---- doc/src/sgml/ref/pg_dumpall.sgml | 4 ++-- doc/src/sgml/ref/pg_passwd.sgml | 4 ++-- doc/src/sgml/ref/pg_upgrade.sgml | 10 +++++----- doc/src/sgml/ref/pgaccess-ref.sgml | 4 ++-- doc/src/sgml/ref/pgtclsh.sgml | 8 ++++---- doc/src/sgml/ref/pgtksh.sgml | 8 ++++---- doc/src/sgml/ref/postgres-ref.sgml | 4 ++-- doc/src/sgml/ref/postmaster.sgml | 4 ++-- doc/src/sgml/ref/psql-ref.sgml | 30 +++++++++++++++--------------- doc/src/sgml/ref/reindex.sgml | 7 ++++--- doc/src/sgml/ref/reset.sgml | 6 +++--- doc/src/sgml/ref/revoke.sgml | 4 ++-- doc/src/sgml/ref/rollback.sgml | 4 ++-- doc/src/sgml/ref/select.sgml | 20 ++++++++++---------- doc/src/sgml/ref/select_into.sgml | 6 +++--- doc/src/sgml/ref/set.sgml | 21 +++++++++++---------- doc/src/sgml/ref/set_transaction.sgml | 10 ++++++---- doc/src/sgml/ref/show.sgml | 6 +++--- doc/src/sgml/ref/truncate.sgml | 4 ++-- doc/src/sgml/ref/unlisten.sgml | 6 +++--- doc/src/sgml/ref/update.sgml | 6 +++--- doc/src/sgml/ref/vacuum.sgml | 8 ++++---- doc/src/sgml/ref/vacuumdb.sgml | 4 ++-- 91 files changed, 360 insertions(+), 340 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/abort.sgml b/doc/src/sgml/ref/abort.sgml index 49cd37d277f..1172653942a 100644 --- a/doc/src/sgml/ref/abort.sgml +++ b/doc/src/sgml/ref/abort.sgml @@ -1,6 +1,6 @@ @@ -129,7 +129,7 @@ ABORT WORK; SQL92 - This command is a Postgres extension present + This command is a PostgreSQL extension present for historical reasons. ROLLBACK is the SQL92 equivalent command. diff --git a/doc/src/sgml/ref/allfiles.sgml b/doc/src/sgml/ref/allfiles.sgml index aea2171cdfc..b7d3fe2a01b 100644 --- a/doc/src/sgml/ref/allfiles.sgml +++ b/doc/src/sgml/ref/allfiles.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/alter_group.sgml b/doc/src/sgml/ref/alter_group.sgml index c2072f8f153..c96a7f79ba0 100644 --- a/doc/src/sgml/ref/alter_group.sgml +++ b/doc/src/sgml/ref/alter_group.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index 7fabba4fb9c..6b1b427fae9 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -1,6 +1,6 @@ @@ -313,7 +313,7 @@ ALTER TABLE distributors ADD CONSTRAINT dist_id_zipcode_key UNIQUE (dist_id, zip SQL92 specifies some additional capabilities for ALTER TABLE - statement which are not yet directly supported by Postgres: + statement which are not yet directly supported by PostgreSQL: @@ -345,7 +345,7 @@ DROP TABLE temp; The clauses to rename tables, columns, indexes, and sequences are - Postgres extensions from SQL92. + PostgreSQL extensions from SQL92. diff --git a/doc/src/sgml/ref/alter_user.sgml b/doc/src/sgml/ref/alter_user.sgml index e7f650f3882..81190578765 100644 --- a/doc/src/sgml/ref/alter_user.sgml +++ b/doc/src/sgml/ref/alter_user.sgml @@ -1,6 +1,6 @@ @@ -155,7 +155,7 @@ ERROR: ALTER USER: user "username" does not exist ALTER USER is used to change the attributes of a user's - Postgres account. Attributes not mentioned + PostgreSQL account. Attributes not mentioned in the command retain their previous settings. diff --git a/doc/src/sgml/ref/analyze.sgml b/doc/src/sgml/ref/analyze.sgml index dba4c1befa2..89628d0b040 100644 --- a/doc/src/sgml/ref/analyze.sgml +++ b/doc/src/sgml/ref/analyze.sgml @@ -1,6 +1,6 @@ @@ -99,7 +99,7 @@ ANALYZE [ VERBOSE ] [ table [ ( ANALYZE collects statistics about the contents of - Postgres tables, and stores the results in + PostgreSQL tables, and stores the results in the system table pg_statistic. Subsequently, the query planner uses the statistics to help determine the most efficient execution plans for queries. diff --git a/doc/src/sgml/ref/begin.sgml b/doc/src/sgml/ref/begin.sgml index b2b9a88d6b1..15c1dbdf070 100644 --- a/doc/src/sgml/ref/begin.sgml +++ b/doc/src/sgml/ref/begin.sgml @@ -1,6 +1,6 @@ @@ -95,7 +95,7 @@ NOTICE: BEGIN: already a transaction in progress - By default, Postgres executes transactions + By default, PostgreSQL executes transactions in unchained mode (also known as autocommit in other database systems). @@ -116,7 +116,7 @@ NOTICE: BEGIN: already a transaction in progress The default transaction isolation level in - Postgres + PostgreSQL is READ COMMITTED, where queries inside the transaction see only changes committed before query execution. So, you have to use SET TRANSACTION ISOLATION LEVEL SERIALIZABLE @@ -128,7 +128,7 @@ NOTICE: BEGIN: already a transaction in progress - If the transaction is committed, Postgres + If the transaction is committed, PostgreSQL will ensure either that all updates are done or else that none of them are done. Transactions have the standard ACID (atomic, consistent, isolatable, and durable) property. @@ -185,7 +185,7 @@ BEGIN WORK; BEGIN - is a Postgres language extension. + is a PostgreSQL language extension. There is no explicit BEGIN command in SQL92; transaction initiation is always implicit and it terminates either diff --git a/doc/src/sgml/ref/close.sgml b/doc/src/sgml/ref/close.sgml index e56e8031304..718209ff3f9 100644 --- a/doc/src/sgml/ref/close.sgml +++ b/doc/src/sgml/ref/close.sgml @@ -1,6 +1,6 @@ @@ -112,7 +112,7 @@ NOTICE PerformPortalClose: portal "cursor - Postgres does not have + PostgreSQL does not have an explicit OPEN cursor statement; a cursor is considered open when it is declared. Use the DECLARE statement to declare a cursor. diff --git a/doc/src/sgml/ref/cluster.sgml b/doc/src/sgml/ref/cluster.sgml index 72dc8033678..82c4d3bcf2c 100644 --- a/doc/src/sgml/ref/cluster.sgml +++ b/doc/src/sgml/ref/cluster.sgml @@ -1,6 +1,6 @@ @@ -114,7 +114,7 @@ ERROR: Relation table does not exis Description - CLUSTER instructs Postgres + CLUSTER instructs PostgreSQL to cluster the table specified by table approximately based on the index specified by @@ -174,7 +174,7 @@ ERROR: Relation table does not exis on large tables because the rows are fetched from the heap in index order, and if the heap table is unordered, the entries are on random pages, so there is one disk page - retrieved for every row moved. Postgres has a cache, + retrieved for every row moved. PostgreSQL has a cache, but the majority of a big table will not fit in the cache. @@ -186,7 +186,7 @@ SELECT columnlist INTO TABLE table ORDER BY columnlist - which uses the Postgres sorting code in + which uses the PostgreSQL sorting code in the ORDER BY clause to match the index, and which is much faster for unordered data. You then drop the old table, use ALTER TABLE...RENAME diff --git a/doc/src/sgml/ref/comment.sgml b/doc/src/sgml/ref/comment.sgml index dc913d49068..af4a3f65885 100644 --- a/doc/src/sgml/ref/comment.sgml +++ b/doc/src/sgml/ref/comment.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/commit.sgml b/doc/src/sgml/ref/commit.sgml index 301fcd0101e..e8a956f6938 100644 --- a/doc/src/sgml/ref/commit.sgml +++ b/doc/src/sgml/ref/commit.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml index df607d500f4..7a49f4cd77f 100644 --- a/doc/src/sgml/ref/copy.sgml +++ b/doc/src/sgml/ref/copy.sgml @@ -1,6 +1,6 @@ @@ -172,7 +172,7 @@ ERROR: reason COPY moves data between - Postgres tables and + PostgreSQL tables and standard file-system files. COPY TO copies the entire contents of a table to @@ -182,7 +182,7 @@ ERROR: reason COPY with a filename instructs - the Postgres backend + the PostgreSQL backend to directly read from or write to a file. The file must be accessible to the backend and the name must be specified from the viewpoint of the backend. @@ -262,7 +262,8 @@ ERROR: reason directly by the backend, not by the client application. Therefore, they must reside on or be accessible to the database server machine, not the client. They must be accessible to and readable or writable - by the Postgres user (the userid the backend runs as), not the client. + by the PostgreSQL user (the userid the + backend runs as), not the client. COPY naming a file is only allowed to database superusers, since it allows writing on any file that the backend has privileges to write on. @@ -343,7 +344,7 @@ ERROR: reason as the column delimiter, backslash that delimiter character to include it in data.) A literal newline character is represented as a backslash and a newline. When loading text data - not generated by Postgres, + not generated by PostgreSQL, you will need to convert backslash characters ("\") to double-backslashes ("\\") to ensure that they are loaded properly. @@ -357,7 +358,8 @@ ERROR: reason Binary Format The file format used for COPY BINARY changed in - Postgres v7.1. The new format consists of a file header, zero or more + PostgreSQL v7.1. + The new format consists of a file header, zero or more tuples, and a file trailer. diff --git a/doc/src/sgml/ref/create_aggregate.sgml b/doc/src/sgml/ref/create_aggregate.sgml index fc8f064f7a1..8c5e3f7f481 100644 --- a/doc/src/sgml/ref/create_aggregate.sgml +++ b/doc/src/sgml/ref/create_aggregate.sgml @@ -1,6 +1,6 @@ @@ -157,7 +157,7 @@ CREATE CREATE AGGREGATE - allows a user or programmer to extend Postgres + allows a user or programmer to extend PostgreSQL functionality by defining new aggregate functions. Some aggregate functions for base types such as min(integer) and avg(double precision) are already provided in the base @@ -185,7 +185,7 @@ CREATE - Postgres creates a temporary variable + PostgreSQL creates a temporary variable of data type stype to hold the current internal state of the aggregate. At each input data item, @@ -284,7 +284,7 @@ CREATE CREATE AGGREGATE - is a Postgres language extension. + is a PostgreSQL language extension. There is no CREATE AGGREGATE in SQL92. diff --git a/doc/src/sgml/ref/create_constraint.sgml b/doc/src/sgml/ref/create_constraint.sgml index 3ffefe4cbd6..0a72f1fa443 100644 --- a/doc/src/sgml/ref/create_constraint.sgml +++ b/doc/src/sgml/ref/create_constraint.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/create_database.sgml b/doc/src/sgml/ref/create_database.sgml index 77fa3fe1c30..1c20644502c 100644 --- a/doc/src/sgml/ref/create_database.sgml +++ b/doc/src/sgml/ref/create_database.sgml @@ -1,6 +1,6 @@ @@ -170,7 +170,7 @@ CREATE DATABASE name CREATE DATABASE creates a new - Postgres database. + PostgreSQL database. The creator becomes the owner of the new database. @@ -201,7 +201,8 @@ CREATE DATABASE name name. In particular, by writing TEMPLATE = template0, you can create a virgin database containing only the standard objects predefined by your - version of Postgres. This is useful if you wish to avoid copying + version of PostgreSQL. This is useful + if you wish to avoid copying any installation-local objects that may have been added to template1. @@ -226,7 +227,7 @@ CREATE DATABASE name Notes - CREATE DATABASE is a Postgres + CREATE DATABASE is a PostgreSQL language extension. @@ -250,7 +251,7 @@ CREATE DATABASE name comment from Olly; response from Thomas... initlocation does not create a PG_VERSION file in the specified location. - How will Postgres handle the situation if it is upgraded to an + How will PostgreSQL handle the situation if it is upgraded to an incompatible database version? Hmm. This isn't an issue since the upgrade would do @@ -287,7 +288,14 @@ comment from Olly; response from Thomas... $ mkdir private_db $ initlocation ~/private_db -Creating Postgres database system directory /home/olly/private_db/base + +The location will be initialized with username "olly". +This user will own all the files and must also own the server process. +Creating directory /home/olly/private_db +Creating directory /home/olly/private_db/base + +initlocation is complete. + $ psql olly diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml index 5a4c49cb633..df643cd8e8b 100644 --- a/doc/src/sgml/ref/create_function.sgml +++ b/doc/src/sgml/ref/create_function.sgml @@ -1,5 +1,5 @@ @@ -200,7 +200,7 @@ CREATE [ OR REPLACE ] FUNCTION name Refer to the chapter in the PostgreSQL Programmer's Guide on the topic of extending - Postgres via functions + PostgreSQL via functions for further information on writing external functions. @@ -215,7 +215,7 @@ CREATE [ OR REPLACE ] FUNCTION name - Postgres allows function overloading; + PostgreSQL allows function overloading; that is, the same name can be used for several different functions so long as they have distinct argument types. This facility must be used with caution for internal and C-language functions, however. diff --git a/doc/src/sgml/ref/create_group.sgml b/doc/src/sgml/ref/create_group.sgml index 6556997022a..1a91013353b 100644 --- a/doc/src/sgml/ref/create_group.sgml +++ b/doc/src/sgml/ref/create_group.sgml @@ -1,6 +1,6 @@ @@ -55,7 +55,7 @@ where option can be: The SYSID clause can be used to choose - the Postgres group id of the new + the PostgreSQL group id of the new group. It is not necessary to do so, however. diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml index e76d87de902..58392864cd1 100644 --- a/doc/src/sgml/ref/create_index.sgml +++ b/doc/src/sgml/ref/create_index.sgml @@ -1,6 +1,6 @@ @@ -78,7 +78,7 @@ CREATE [ UNIQUE ] INDEX index_name The name of the access method to be used for the index. The default access method is BTREE. - Postgres provides four access methods for indexes: + PostgreSQL provides four access methods for indexes: @@ -236,7 +236,7 @@ ERROR: Cannot create index: 'index_name' already exists. - Postgres provides btree, rtree, hash, and GiST access methods for + PostgreSQL provides btree, rtree, hash, and GiST access methods for indexes. The btree access method is an implementation of Lehman-Yao high-concurrency btrees. The rtree access method implements standard rtrees using Guttman's quadratic split algorithm. @@ -292,7 +292,7 @@ ERROR: Cannot create index: 'index_name' already exists. - The Postgres + The PostgreSQL query optimizer will consider using a btree index whenever an indexed attribute is involved in a comparison using one of: @@ -306,7 +306,7 @@ ERROR: Cannot create index: 'index_name' already exists. - The Postgres + The PostgreSQL query optimizer will consider using an rtree index whenever an indexed attribute is involved in a comparison using one of: @@ -322,7 +322,7 @@ ERROR: Cannot create index: 'index_name' already exists. - The Postgres + The PostgreSQL query optimizer will consider using a hash index whenever an indexed attribute is involved in a comparison using the = operator. @@ -331,7 +331,8 @@ ERROR: Cannot create index: 'index_name' already exists. Currently, only the btree and gist access methods support multi-column indexes. Up to 16 keys may be specified by default (this limit - can be altered when building Postgres). Only btree currently supports + can be altered when building + PostgreSQL). Only btree currently supports unique indexes. @@ -428,7 +429,7 @@ SELECT * FROM points SQL92 - CREATE INDEX is a Postgres language extension. + CREATE INDEX is a PostgreSQL language extension. There is no CREATE INDEX command in SQL92. diff --git a/doc/src/sgml/ref/create_language.sgml b/doc/src/sgml/ref/create_language.sgml index 922e5275caf..3d2b71198fc 100644 --- a/doc/src/sgml/ref/create_language.sgml +++ b/doc/src/sgml/ref/create_language.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/create_operator.sgml b/doc/src/sgml/ref/create_operator.sgml index 40c9799772f..11debc3d3a7 100644 --- a/doc/src/sgml/ref/create_operator.sgml +++ b/doc/src/sgml/ref/create_operator.sgml @@ -1,6 +1,6 @@ @@ -205,7 +205,7 @@ CREATE For example, @- is an allowed operator name, but *- is not. - This restriction allows Postgres to + This restriction allows PostgreSQL to parse SQL-compliant queries without requiring spaces between tokens. @@ -218,7 +218,7 @@ CREATE For example, if you have defined a left-unary operator named @, you cannot write X*@Y; you must write X* @Y to ensure that - Postgres reads it as two operator names + PostgreSQL reads it as two operator names not one. @@ -242,7 +242,7 @@ CREATE The commutator operator should be identified if one exists, - so that Postgres can + so that PostgreSQL can reverse the order of the operands if it wishes. For example, the operator area-less-than, <<<, would probably have a commutator @@ -280,7 +280,7 @@ MYBOXES.description !== box '((0,0), (1,1))' If a commutator operator name is supplied, - Postgres + PostgreSQL searches for it in the catalog. If it is found and it does not yet have a commutator itself, then the commutator's entry is updated to have the newly created operator as its @@ -290,17 +290,18 @@ MYBOXES.description !== box '((0,0), (1,1))' operator should be defined without a commutator or negator (as appropriate). When the second operator is defined, name the first as the commutator or negator. The first - will be updated as a side effect. (As of Postgres 6.5, + will be updated as a side effect. (As of + PostgreSQL 6.5, it also works to just have both operators refer to each other.) The HASHES, SORT1, and SORT2 options are present to support the query optimizer in performing joins. - Postgres can always + PostgreSQL can always evaluate a join (i.e., processing a clause with two tuple variables separated by an operator that returns a boolean) by iterative substitution [WONG76]. - In addition, Postgres + In addition, PostgreSQL can use a hash-join algorithm along the lines of [SHAP86]; however, it must know whether this strategy is applicable. The current hash-join algorithm @@ -321,7 +322,7 @@ MYBOXES.description !== box '((0,0), (1,1))' If other join strategies are found to be practical, - Postgres + PostgreSQL will change the optimizer and run-time system to use them and will require additional specification when an operator is defined. Fortunately, the research community @@ -336,7 +337,7 @@ MYBOXES.description !== box '((0,0), (1,1))' MYBOXES.description <<< box '((0,0), (1,1))' is present in the qualification, - then Postgres may have to + then PostgreSQL may have to estimate the fraction of the instances in MYBOXES that satisfy the clause. The function res_proc @@ -364,7 +365,7 @@ my_procedure_1 (MYBOXES.description, box '((0,0), (1,1))') MYBOXES.description === box '((0,0), (1,1))' - is that Postgres + is that PostgreSQL attempts to optimize operators and can decide to use an index to restrict the search space when operators are involved. However, there is no attempt to @@ -428,7 +429,7 @@ CREATE OPERATOR === ( CREATE OPERATOR - is a Postgres extension. + is a PostgreSQL extension. There is no CREATE OPERATOR statement in SQL92. diff --git a/doc/src/sgml/ref/create_rule.sgml b/doc/src/sgml/ref/create_rule.sgml index ee17fbdded1..0890faa9cec 100644 --- a/doc/src/sgml/ref/create_rule.sgml +++ b/doc/src/sgml/ref/create_rule.sgml @@ -1,6 +1,6 @@ @@ -148,7 +148,7 @@ CREATE - The Postgres + The PostgreSQL rule system allows one to define an alternate action to be performed on inserts, updates, or deletions from database tables. Rules are used to @@ -255,8 +255,8 @@ CREATE It is very important to take care to avoid circular rules. For example, though each of the following two rule definitions are accepted by - Postgres, the - select command will cause Postgres to + PostgreSQL, the + select command will cause PostgreSQL to report an error because the query cycled too many times: @@ -272,7 +272,7 @@ CREATE RULE "_RETtoyemp" AS This attempt to select from EMP will cause - Postgres to issue an error + PostgreSQL to issue an error because the queries cycled too many times: @@ -310,7 +310,7 @@ UPDATE mytable SET name = 'foo' WHERE id = 42; - CREATE RULE statement is a Postgres + CREATE RULE statement is a PostgreSQL language extension. There is no CREATE RULE statement in SQL92. diff --git a/doc/src/sgml/ref/create_sequence.sgml b/doc/src/sgml/ref/create_sequence.sgml index f2e343660d8..e528658d0dd 100644 --- a/doc/src/sgml/ref/create_sequence.sgml +++ b/doc/src/sgml/ref/create_sequence.sgml @@ -1,6 +1,6 @@ @@ -362,7 +362,7 @@ END; - CREATE SEQUENCE is a Postgres + CREATE SEQUENCE is a PostgreSQL language extension. There is no CREATE SEQUENCE statement in SQL92. diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index e583c188dd2..ec264dbb118 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -1,6 +1,6 @@ @@ -186,7 +186,8 @@ and table_constraint is: diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml index ff587643a9d..846bc5cf877 100644 --- a/doc/src/sgml/ref/create_trigger.sgml +++ b/doc/src/sgml/ref/create_trigger.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/create_type.sgml b/doc/src/sgml/ref/create_type.sgml index 0ae5a560b40..916163c1dd0 100644 --- a/doc/src/sgml/ref/create_type.sgml +++ b/doc/src/sgml/ref/create_type.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/create_user.sgml b/doc/src/sgml/ref/create_user.sgml index 34e210c70e8..cc23cce03b8 100644 --- a/doc/src/sgml/ref/create_user.sgml +++ b/doc/src/sgml/ref/create_user.sgml @@ -1,6 +1,6 @@ @@ -59,7 +59,7 @@ where option can be: The SYSID clause can be used to choose - the Postgres user id of the user + the PostgreSQL user id of the user that is being created. It is not at all necessary that those match the UNIX user ids, but some people choose to keep the numbers the same. @@ -193,7 +193,7 @@ where option can be: CREATE USER will add a new user to an instance of - Postgres. Refer to the administrator's + PostgreSQL. Refer to the administrator's guide for information about managing users and authentication. You must be a database superuser to use this command. @@ -203,7 +203,7 @@ where option can be: endterm="SQL-DROPUSER-title"> to remove a user. Use to add or remove the user from other groups. - Postgres + PostgreSQL comes with a script which has the same functionality as this command (in fact, it calls this command) diff --git a/doc/src/sgml/ref/create_view.sgml b/doc/src/sgml/ref/create_view.sgml index cc533e1824f..c0d60f3e92c 100644 --- a/doc/src/sgml/ref/create_view.sgml +++ b/doc/src/sgml/ref/create_view.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/createdb.sgml b/doc/src/sgml/ref/createdb.sgml index 57c244b271d..6b14b268377 100644 --- a/doc/src/sgml/ref/createdb.sgml +++ b/doc/src/sgml/ref/createdb.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/createlang.sgml b/doc/src/sgml/ref/createlang.sgml index 4d267f75d1a..3c9f84d183d 100644 --- a/doc/src/sgml/ref/createlang.sgml +++ b/doc/src/sgml/ref/createlang.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/createuser.sgml b/doc/src/sgml/ref/createuser.sgml index 8efa8c39373..9dcb7a1bb93 100644 --- a/doc/src/sgml/ref/createuser.sgml +++ b/doc/src/sgml/ref/createuser.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/current_time.sgml b/doc/src/sgml/ref/current_time.sgml index 617b3dba911..773a34f5ce6 100644 --- a/doc/src/sgml/ref/current_time.sgml +++ b/doc/src/sgml/ref/current_time.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/current_timestamp.sgml b/doc/src/sgml/ref/current_timestamp.sgml index 23438218022..2be1b05a567 100644 --- a/doc/src/sgml/ref/current_timestamp.sgml +++ b/doc/src/sgml/ref/current_timestamp.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/current_user.sgml b/doc/src/sgml/ref/current_user.sgml index 62a44986b33..8fa3ebc48a9 100644 --- a/doc/src/sgml/ref/current_user.sgml +++ b/doc/src/sgml/ref/current_user.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/declare.sgml b/doc/src/sgml/ref/declare.sgml index e3b7b1d4a3c..692656af9c4 100644 --- a/doc/src/sgml/ref/declare.sgml +++ b/doc/src/sgml/ref/declare.sgml @@ -1,6 +1,6 @@ @@ -62,7 +62,7 @@ DECLARE cursorname [ BINARY ] [ INS SQL92 keyword indicating that data retrieved from the cursor should be unaffected by updates from other processes or cursors. Since cursor operations occur within transactions - in Postgres this is always the case. + in PostgreSQL this is always the case. This keyword has no effect. @@ -74,7 +74,7 @@ DECLARE cursorname [ BINARY ] [ INS SQL92 keyword indicating that data may be retrieved in multiple rows per FETCH operation. Since this is allowed at all times - by Postgres this keyword has no effect. + by PostgreSQL this keyword has no effect. @@ -97,7 +97,7 @@ DECLARE cursorname [ BINARY ] [ INS SQL92 keyword indicating that the cursor will be used in a read only mode. Since this is the only cursor access mode - available in Postgres this keyword has no effect. + available in PostgreSQL this keyword has no effect. @@ -108,7 +108,7 @@ DECLARE cursorname [ BINARY ] [ INS SQL92 keyword indicating that the cursor will be used to update tables. Since cursor updates are not currently - supported in Postgres this keyword + supported in PostgreSQL this keyword provokes an informational error message. @@ -120,7 +120,7 @@ DECLARE cursorname [ BINARY ] [ INS Column(s) to be updated. Since cursor updates are not currently - supported in Postgres the UPDATE clause + supported in PostgreSQL the UPDATE clause provokes an informational error message. @@ -196,7 +196,7 @@ ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks Normal cursors return data in text format, either ASCII or another - encoding scheme depending on how the Postgres + encoding scheme depending on how the PostgreSQL backend was built. Since data is stored natively in binary format, the system must do a conversion to produce the text format. In addition, @@ -224,7 +224,7 @@ ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks String representation is architecture-neutral whereas binary representation can differ between different machine architectures. - Postgres does not resolve + PostgreSQL does not resolve byte ordering or representation issues for binary cursors. Therefore, if your client machine and server machine use different representations (e.g., big-endian versus little-endian), @@ -263,11 +263,11 @@ ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks In SQL92 cursors are only available in embedded SQL (ESQL) applications. - The Postgres backend + The PostgreSQL backend does not implement an explicit OPEN cursor statement; a cursor is considered to be open when it is declared. However, ecpg, the - embedded SQL preprocessor for Postgres, + embedded SQL preprocessor for PostgreSQL, supports the SQL92 cursor conventions, including those involving DECLARE and OPEN statements. @@ -302,12 +302,12 @@ DECLARE liahona CURSOR SQL92 allows cursors only in embedded SQL - and in modules. Postgres permits cursors to be used + and in modules. PostgreSQL permits cursors to be used interactively. SQL92 allows embedded or modular cursors to update database information. - All Postgres cursors are read only. - The BINARY keyword is a Postgres extension. + All PostgreSQL cursors are read only. + The BINARY keyword is a PostgreSQL extension. diff --git a/doc/src/sgml/ref/delete.sgml b/doc/src/sgml/ref/delete.sgml index 3597db386b8..ac5c699cf8e 100644 --- a/doc/src/sgml/ref/delete.sgml +++ b/doc/src/sgml/ref/delete.sgml @@ -1,6 +1,6 @@ @@ -110,7 +110,7 @@ DELETE count is a - Postgres extension which provides a + PostgreSQL extension which provides a faster mechanism to remove all rows from a table. @@ -187,7 +187,7 @@ DELETE FROM table WHERE where cursor identifies an open cursor. - Interactive cursors in Postgres are read-only. + Interactive cursors in PostgreSQL are read-only. diff --git a/doc/src/sgml/ref/drop_aggregate.sgml b/doc/src/sgml/ref/drop_aggregate.sgml index 937d6ac4948..d60c9cb8f44 100644 --- a/doc/src/sgml/ref/drop_aggregate.sgml +++ b/doc/src/sgml/ref/drop_aggregate.sgml @@ -1,6 +1,6 @@ @@ -153,7 +153,7 @@ DROP AGGREGATE myavg(int4); There is no DROP AGGREGATE statement in SQL92; the statement is a - Postgres + PostgreSQL language extension. diff --git a/doc/src/sgml/ref/drop_database.sgml b/doc/src/sgml/ref/drop_database.sgml index 07d596c6268..f68349a05a2 100644 --- a/doc/src/sgml/ref/drop_database.sgml +++ b/doc/src/sgml/ref/drop_database.sgml @@ -1,6 +1,6 @@ @@ -148,7 +148,7 @@ DROP DATABASE name DROP DATABASE statement is a - Postgres language extension; + PostgreSQL language extension; there is no such command in SQL92. diff --git a/doc/src/sgml/ref/drop_function.sgml b/doc/src/sgml/ref/drop_function.sgml index 6e92205eefd..34de6e73055 100644 --- a/doc/src/sgml/ref/drop_function.sgml +++ b/doc/src/sgml/ref/drop_function.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/drop_group.sgml b/doc/src/sgml/ref/drop_group.sgml index e39ff0e1870..16f7496bdd8 100644 --- a/doc/src/sgml/ref/drop_group.sgml +++ b/doc/src/sgml/ref/drop_group.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/drop_index.sgml b/doc/src/sgml/ref/drop_index.sgml index 0fdce31e0fd..210753b49ad 100644 --- a/doc/src/sgml/ref/drop_index.sgml +++ b/doc/src/sgml/ref/drop_index.sgml @@ -1,6 +1,6 @@ @@ -103,7 +103,7 @@ ERROR: index "index_name" does not Notes - DROP INDEX is a Postgres + DROP INDEX is a PostgreSQL language extension. diff --git a/doc/src/sgml/ref/drop_language.sgml b/doc/src/sgml/ref/drop_language.sgml index 2f85007af8d..26668d5995c 100644 --- a/doc/src/sgml/ref/drop_language.sgml +++ b/doc/src/sgml/ref/drop_language.sgml @@ -1,6 +1,6 @@ @@ -105,7 +105,7 @@ ERROR: Language "name" doesn't exis The DROP PROCEDURAL LANGUAGE statement is - a Postgres language extension. + a PostgreSQL language extension. Refer to diff --git a/doc/src/sgml/ref/drop_operator.sgml b/doc/src/sgml/ref/drop_operator.sgml index 23e39f434b3..715e2e4d814 100644 --- a/doc/src/sgml/ref/drop_operator.sgml +++ b/doc/src/sgml/ref/drop_operator.sgml @@ -1,6 +1,6 @@ @@ -149,7 +149,7 @@ ERROR: RemoveOperator: right unary operator 'oper The DROP OPERATOR statement is a - Postgres + PostgreSQL language extension. diff --git a/doc/src/sgml/ref/drop_rule.sgml b/doc/src/sgml/ref/drop_rule.sgml index 6063c114abc..452ff48a18d 100644 --- a/doc/src/sgml/ref/drop_rule.sgml +++ b/doc/src/sgml/ref/drop_rule.sgml @@ -1,6 +1,6 @@ @@ -90,8 +90,8 @@ ERROR: Rule or view "name" not fou DROP RULE drops a rule from the specified - Postgres rule - system. Postgres + PostgreSQL rule + system. PostgreSQL will immediately cease enforcing it and will purge its definition from the system catalogs. @@ -105,7 +105,7 @@ ERROR: Rule or view "name" not fou The DROP RULE statement is a - Postgres + PostgreSQL language extension. diff --git a/doc/src/sgml/ref/drop_sequence.sgml b/doc/src/sgml/ref/drop_sequence.sgml index 5782fdc6a26..70bb2034b8c 100644 --- a/doc/src/sgml/ref/drop_sequence.sgml +++ b/doc/src/sgml/ref/drop_sequence.sgml @@ -1,6 +1,6 @@ @@ -105,7 +105,7 @@ ERROR: sequence "name" does not exi The DROP SEQUENCE statement is a - Postgres + PostgreSQL language extension. diff --git a/doc/src/sgml/ref/drop_table.sgml b/doc/src/sgml/ref/drop_table.sgml index 0899c5a7d40..a462fff51af 100644 --- a/doc/src/sgml/ref/drop_table.sgml +++ b/doc/src/sgml/ref/drop_table.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/drop_trigger.sgml b/doc/src/sgml/ref/drop_trigger.sgml index f1bfdadf61f..3811e2dcc26 100644 --- a/doc/src/sgml/ref/drop_trigger.sgml +++ b/doc/src/sgml/ref/drop_trigger.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/drop_type.sgml b/doc/src/sgml/ref/drop_type.sgml index 8bf9a8f382b..997607b1aea 100644 --- a/doc/src/sgml/ref/drop_type.sgml +++ b/doc/src/sgml/ref/drop_type.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/drop_user.sgml b/doc/src/sgml/ref/drop_user.sgml index 9c7cc4c58ca..2a20e55eed9 100644 --- a/doc/src/sgml/ref/drop_user.sgml +++ b/doc/src/sgml/ref/drop_user.sgml @@ -1,6 +1,6 @@ @@ -109,7 +109,7 @@ DROP USER: user "name" owns databas Use to add new users, and to change a user's properties. - Postgres + PostgreSQL comes with a script which has the same functionality as this command (in fact, it calls this command) diff --git a/doc/src/sgml/ref/drop_view.sgml b/doc/src/sgml/ref/drop_view.sgml index 918da7c5e00..394147e6999 100644 --- a/doc/src/sgml/ref/drop_view.sgml +++ b/doc/src/sgml/ref/drop_view.sgml @@ -1,6 +1,6 @@ @@ -184,7 +184,7 @@ DROP VIEW view { RESTRICT | CASCADE At present, to remove a referenced view from a - Postgres database, + PostgreSQL database, you must drop it explicitly. diff --git a/doc/src/sgml/ref/dropdb.sgml b/doc/src/sgml/ref/dropdb.sgml index c9df28445b8..79750a900bd 100644 --- a/doc/src/sgml/ref/dropdb.sgml +++ b/doc/src/sgml/ref/dropdb.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/droplang.sgml b/doc/src/sgml/ref/droplang.sgml index 3fe3dc8ad62..27cea628fe3 100644 --- a/doc/src/sgml/ref/droplang.sgml +++ b/doc/src/sgml/ref/droplang.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/dropuser.sgml b/doc/src/sgml/ref/dropuser.sgml index 217040403d6..07d77691ea5 100644 --- a/doc/src/sgml/ref/dropuser.sgml +++ b/doc/src/sgml/ref/dropuser.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/ecpg-ref.sgml b/doc/src/sgml/ref/ecpg-ref.sgml index a9d27061785..71a277d032d 100644 --- a/doc/src/sgml/ref/ecpg-ref.sgml +++ b/doc/src/sgml/ref/ecpg-ref.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/end.sgml b/doc/src/sgml/ref/end.sgml index 9f3bd5db294..119ce8235f5 100644 --- a/doc/src/sgml/ref/end.sgml +++ b/doc/src/sgml/ref/end.sgml @@ -1,6 +1,6 @@ @@ -94,7 +94,7 @@ NOTICE: COMMIT: no transaction in progress - END is a Postgres + END is a PostgreSQL extension, and is a synonym for the SQL92-compatible . diff --git a/doc/src/sgml/ref/explain.sgml b/doc/src/sgml/ref/explain.sgml index b24863529b3..5a4e2771ec8 100644 --- a/doc/src/sgml/ref/explain.sgml +++ b/doc/src/sgml/ref/explain.sgml @@ -1,6 +1,6 @@ @@ -82,7 +82,7 @@ NOTICE: QUERY PLAN: - Explicit query plan from the Postgres backend. + Explicit query plan from the PostgreSQL backend. @@ -110,7 +110,8 @@ EXPLAIN - This command displays the execution plan that the Postgres planner + This command displays the execution plan that the + PostgreSQL planner generates for the supplied query. The execution plan shows how the table(s) referenced by the query will be scanned---by plain sequential scan, index scan, etc.---and if multiple tables are @@ -143,7 +144,8 @@ EXPLAIN The VERBOSE option emits the full internal representation of the plan tree, rather than just a summary (and sends it to the postmaster log file, too). - Usually this option is only useful for debugging Postgres. + Usually this option is only useful for debugging + PostgreSQL. @@ -172,7 +174,7 @@ ROLLBACK; There is only sparse documentation on the optimizer's use of cost - information in Postgres. + information in PostgreSQL. Refer to the User's Guide and Programmer's Guide for more information. @@ -236,7 +238,8 @@ Aggregate (cost=0.42..0.42 rows=1 width=4) Note that the specific numbers shown, and even the selected query - strategy, may vary between Postgres releases due to planner improvements. + strategy, may vary between PostgreSQL + releases due to planner improvements. diff --git a/doc/src/sgml/ref/fetch.sgml b/doc/src/sgml/ref/fetch.sgml index e3e5f77b5af..85f8fbb00a1 100644 --- a/doc/src/sgml/ref/fetch.sgml +++ b/doc/src/sgml/ref/fetch.sgml @@ -1,6 +1,6 @@ @@ -175,7 +175,7 @@ NOTICE: FETCH/ABSOLUTE not supported, using RELATIVE - Postgres does not support absolute + PostgreSQL does not support absolute positioning of cursors. @@ -195,10 +195,10 @@ FETCH RELATIVE 0 FROM cursor. - Postgres does not currently support + PostgreSQL does not currently support this notion; in fact the value zero is reserved to indicate that all rows should be retrieved and is equivalent to specifying the ALL keyword. - If the RELATIVE keyword has been used, Postgres + If the RELATIVE keyword has been used, PostgreSQL assumes that the user intended SQL92 behavior and returns this error message. @@ -250,7 +250,7 @@ FETCH RELATIVE 0 FROM cursor. Note that the FORWARD and BACKWARD keywords are - Postgres extensions. + PostgreSQL extensions. The SQL92 syntax is also supported, specified in the second form of the command. See below for details on compatibility issues. @@ -258,7 +258,7 @@ FETCH RELATIVE 0 FROM cursor. Updating data in a cursor is not supported by - Postgres, + PostgreSQL, because mapping cursor updates back to base tables is not generally possible, as is also the case with VIEW updates. Consequently, @@ -346,7 +346,7 @@ COMMIT WORK; - The non-embedded use of cursors is a Postgres + The non-embedded use of cursors is a PostgreSQL extension. The syntax and usage of cursors is being compared against the embedded form of cursors defined in SQL92. @@ -369,7 +369,7 @@ FETCH ABSOLUTE # The cursor should be positioned to the specified absolute - row number. All row numbers in Postgres + row number. All row numbers in PostgreSQL are relative numbers so this capability is not supported. diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml index a4ff54b5794..98072ee8e02 100644 --- a/doc/src/sgml/ref/grant.sgml +++ b/doc/src/sgml/ref/grant.sgml @@ -1,6 +1,6 @@ @@ -155,7 +155,7 @@ GRANT { { SELECT | INSERT | UPDATE | DELETE | RULE | REFERENCES | TRIGGER } [,.. Notes - Currently, to grant privileges in Postgres + Currently, to grant privileges in PostgreSQL to only a few columns, you must create a view having the desired columns and then grant privileges to that view. diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml index a52a63e53b8..3bbe44aeee8 100644 --- a/doc/src/sgml/ref/initdb.sgml +++ b/doc/src/sgml/ref/initdb.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/initlocation.sgml b/doc/src/sgml/ref/initlocation.sgml index de7e46a6357..7ccb76ed193 100644 --- a/doc/src/sgml/ref/initlocation.sgml +++ b/doc/src/sgml/ref/initlocation.sgml @@ -1,6 +1,6 @@ @@ -30,7 +30,7 @@ Postgres documentation Description initlocation - creates a new Postgres secondary database storage area. + creates a new PostgreSQL secondary database storage area. See the discussion under about how to manage and use secondary storage areas. If the argument does not contain a slash and is not valid as a path, it is assumed to be an environment variable, diff --git a/doc/src/sgml/ref/insert.sgml b/doc/src/sgml/ref/insert.sgml index aad43dd0107..7788d91cf26 100644 --- a/doc/src/sgml/ref/insert.sgml +++ b/doc/src/sgml/ref/insert.sgml @@ -1,6 +1,6 @@ @@ -135,7 +135,7 @@ INSERT 0 # Each column not present in the target list will be inserted using a default value, either a declared DEFAULT value - or NULL. Postgres will reject the new + or NULL. PostgreSQL will reject the new column if a NULL is inserted into a column declared NOT NULL. diff --git a/doc/src/sgml/ref/ipcclean.sgml b/doc/src/sgml/ref/ipcclean.sgml index 7c4fc5647e7..17b10b72aa4 100644 --- a/doc/src/sgml/ref/ipcclean.sgml +++ b/doc/src/sgml/ref/ipcclean.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/listen.sgml b/doc/src/sgml/ref/listen.sgml index 4497f1d67a5..dfa6ecbaf98 100644 --- a/doc/src/sgml/ref/listen.sgml +++ b/doc/src/sgml/ref/listen.sgml @@ -1,6 +1,6 @@ @@ -93,7 +93,7 @@ NOTICE Async_Listen: We are already listening on LISTEN registers the current - Postgres backend as a + PostgreSQL backend as a listener on the notify condition name. @@ -116,7 +116,7 @@ NOTICE Async_Listen: We are already listening on The method a frontend application must use to detect notify events depends on - which Postgres application programming interface it + which PostgreSQL application programming interface it uses. With the basic libpq library, the application issues LISTEN as an ordinary SQL command, and then must periodically call the routine PQnotifies to find out @@ -152,7 +152,7 @@ NOTICE Async_Listen: We are already listening on In some previous releases of - Postgres, + PostgreSQL, name had to be enclosed in double-quotes when it did not correspond to any existing table name, even if syntactically valid as a name. That is no longer required. diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml index c8afdd26433..055977f7457 100644 --- a/doc/src/sgml/ref/lock.sgml +++ b/doc/src/sgml/ref/lock.sgml @@ -1,6 +1,6 @@ @@ -257,7 +257,7 @@ ERROR name: Table does not exist. LOCK TABLE controls concurrent access to a table for the duration of a transaction. - Postgres always uses the least restrictive + PostgreSQL always uses the least restrictive lock mode whenever possible. LOCK TABLE provides for cases when you might need more restrictive locking. @@ -379,7 +379,7 @@ ERROR name: Table does not exist. - Postgres does detect deadlocks and will + PostgreSQL does detect deadlocks and will rollback at least one waiting transaction to resolve the deadlock. @@ -399,13 +399,13 @@ ERROR name: Table does not exist. - LOCK is a Postgres + LOCK is a PostgreSQL language extension. Except for ACCESS SHARE, ACCESS EXCLUSIVE, and SHARE UPDATE EXCLUSIVE lock - modes, the Postgres lock modes and the + modes, the PostgreSQL lock modes and the LOCK TABLE syntax are compatible with those present in Oracle. diff --git a/doc/src/sgml/ref/move.sgml b/doc/src/sgml/ref/move.sgml index 23dec1f6775..78dfb0da580 100644 --- a/doc/src/sgml/ref/move.sgml +++ b/doc/src/sgml/ref/move.sgml @@ -1,6 +1,6 @@ @@ -57,7 +57,7 @@ MOVE [ direction ] [ - MOVE is a Postgres + MOVE is a PostgreSQL language extension. diff --git a/doc/src/sgml/ref/notify.sgml b/doc/src/sgml/ref/notify.sgml index 067f3732a5e..ee2f2bf9b76 100644 --- a/doc/src/sgml/ref/notify.sgml +++ b/doc/src/sgml/ref/notify.sgml @@ -1,6 +1,6 @@ @@ -112,7 +112,7 @@ NOTIFY NOTIFY provides a simple form of signal or IPC (interprocess communication) mechanism for a collection of processes - accessing the same Postgres database. + accessing the same PostgreSQL database. Higher-level mechanisms can be built by using tables in the database to pass additional data (beyond a mere condition name) from notifier to listener(s). @@ -158,13 +158,13 @@ NOTIFY notify event, just like all the other listening frontends. Depending on the application logic, this could result in useless work---for example, re-reading a database table to find the same updates that that frontend just - wrote out. In Postgres 6.4 and later, it is + wrote out. In PostgreSQL 6.4 and later, it is possible to avoid such extra work by noticing whether the notifying backend process's PID (supplied in the notify event message) is the same as one's own backend's PID (available from libpq). When they are the same, the notify event is one's own work bouncing back, and can be ignored. (Despite what was said in the preceding paragraph, this is a safe technique. - Postgres keeps self-notifies separate from notifies + PostgreSQL keeps self-notifies separate from notifies arriving from other backends, so you cannot miss an outside notify by ignoring your own notifies.) @@ -186,13 +186,13 @@ NOTIFY In some previous releases of - Postgres, + PostgreSQL, name had to be enclosed in double-quotes when it did not correspond to any existing table name, even if syntactically valid as a name. That is no longer required. - In Postgres releases prior to 6.4, the backend + In PostgreSQL releases prior to 6.4, the backend PID delivered in a notify message was always the PID of the frontend's own backend. So it was not possible to distinguish one's own notifies from other clients' notifies in those earlier releases. diff --git a/doc/src/sgml/ref/pg_ctl-ref.sgml b/doc/src/sgml/ref/pg_ctl-ref.sgml index 8bcb64e0074..63b57fc11d7 100644 --- a/doc/src/sgml/ref/pg_ctl-ref.sgml +++ b/doc/src/sgml/ref/pg_ctl-ref.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index dff18523e0d..9aadae36e03 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -1,6 +1,6 @@ @@ -670,9 +670,9 @@ connectDBStart() -- connect() failed: No such file or directory The pg_dump utility first appeared in - Postgres95 release 0.02. The + Postgres95 release 0.02. The non-plain-text output formats were introduced in - PostgreSQL 7.1. + PostgreSQL release 7.1. diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml index 9039b36318c..21b6e035f67 100644 --- a/doc/src/sgml/ref/pg_dumpall.sgml +++ b/doc/src/sgml/ref/pg_dumpall.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/pg_passwd.sgml b/doc/src/sgml/ref/pg_passwd.sgml index 0b7aba901f2..13125b08e27 100644 --- a/doc/src/sgml/ref/pg_passwd.sgml +++ b/doc/src/sgml/ref/pg_passwd.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/pg_upgrade.sgml b/doc/src/sgml/ref/pg_upgrade.sgml index 7128604a9c1..2b9406958c9 100644 --- a/doc/src/sgml/ref/pg_upgrade.sgml +++ b/doc/src/sgml/ref/pg_upgrade.sgml @@ -1,6 +1,6 @@ @@ -39,13 +39,13 @@ pg_upgrade [ -f filename ] pg_upgrade is a utility for upgrading from a previous - Postgres release without reloading all the data. - Not all Postgres release transitions can be + PostgreSQL release without reloading all the data. + Not all PostgreSQL release transitions can be handled this way. Check the release notes for details on your installation. - Upgrading <productname>Postgres</productname> with pg_upgrade + Upgrading <productname>PostgreSQL</productname> with pg_upgrade diff --git a/doc/src/sgml/ref/pgaccess-ref.sgml b/doc/src/sgml/ref/pgaccess-ref.sgml index c2f42527c58..29215683fa8 100644 --- a/doc/src/sgml/ref/pgaccess-ref.sgml +++ b/doc/src/sgml/ref/pgaccess-ref.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/pgtclsh.sgml b/doc/src/sgml/ref/pgtclsh.sgml index 39767128a22..5494dd7783e 100644 --- a/doc/src/sgml/ref/pgtclsh.sgml +++ b/doc/src/sgml/ref/pgtclsh.sgml @@ -1,6 +1,6 @@ @@ -38,7 +38,7 @@ Postgres documentation pgtclsh is a Tcl shell interface extended with - Postgres database access functions. + PostgreSQL database access functions. (Essentially, it is tclsh with libpgtcl loaded.) Like with the regular Tcl shell, the first command line @@ -50,7 +50,7 @@ Postgres documentation A Tcl shell with Tk and - Postgres functions is available as PostgreSQL functions is available as . diff --git a/doc/src/sgml/ref/pgtksh.sgml b/doc/src/sgml/ref/pgtksh.sgml index a9856427059..81d1de9291d 100644 --- a/doc/src/sgml/ref/pgtksh.sgml +++ b/doc/src/sgml/ref/pgtksh.sgml @@ -1,6 +1,6 @@ @@ -37,7 +37,7 @@ Postgres documentation pgtksh is a Tcl/Tk - shell interface extended with Postgres + shell interface extended with PostgreSQL database access functions. (Essentially, it is wish with libpgtcl loaded.) Like with wish, the regular @@ -50,7 +50,7 @@ Postgres documentation A plain Tcl shell with - Postgres functions is available as PostgreSQL functions is available as . diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml index 48ff1cb007c..33e9b462373 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/postmaster.sgml b/doc/src/sgml/ref/postmaster.sgml index 6399d3558e9..a693164825c 100644 --- a/doc/src/sgml/ref/postmaster.sgml +++ b/doc/src/sgml/ref/postmaster.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index 55c71a39b12..230e11013bf 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -1,6 +1,6 @@ @@ -37,8 +37,8 @@ Postgres documentation psql is a terminal-based front-end to - Postgres. It enables you to type in queries - interactively, issue them to Postgres, and see + PostgreSQL. It enables you to type in queries + interactively, issue them to PostgreSQL, and see the query results. Alternatively, input can be from a file. In addition, it provides a number of meta-commands and various shell-like features to facilitate writing scripts and automating a wide @@ -64,7 +64,7 @@ Postgres documentation Connecting To A Database - psql is a regular Postgres + psql is a regular PostgreSQL client application. In order to connect to a database you need to know the name of your target database, the hostname and port number of the server and what user name you want to connect as. psql can be @@ -334,7 +334,7 @@ testdb=> \copyright - Shows the copyright and distribution terms of Postgres. + Shows the copyright and distribution terms of PostgreSQL. @@ -406,7 +406,7 @@ testdb=> - Postgres stores the object descriptions in the + PostgreSQL stores the object descriptions in the pg_description system table. @@ -662,7 +662,7 @@ pipe (|). See also \pset for a generic way List all the databases in the server as well as their owners. Append a + to the command name to see any descriptions - for the databases as well. If your Postgres + for the databases as well. If your PostgreSQL installation was compiled with multibyte encoding support, the encoding scheme of each database is shown as well. @@ -702,7 +702,7 @@ pipe (|). See also \pset for a generic way - Stores the file into a Postgres large object. + Stores the file into a PostgreSQL large object. Optionally, it associates the given comment with the object. Example: foo=> \lo_import '/home/peter/pictures/photo.xcf' 'a picture of me' @@ -734,7 +734,7 @@ lo_import 152801 \lo_list - Shows a list of all Postgres large + Shows a list of all PostgreSQL large objects currently stored in the database, along with any comments provided for them. @@ -1718,7 +1718,7 @@ bar When this variable is set and a backslash command queries the database, the query - is first shown. This way you can study the Postgres + is first shown. This way you can study the PostgreSQL internals and provide similar functionality in your own programs. If you set the variable to the value noexec, the queries are just shown but are not actually sent to the backend and executed. @@ -1814,7 +1814,7 @@ bar LO_TRANSACTION - If you use the Postgres large object + If you use the PostgreSQL large object interface to specially store data that does not fit into one tuple, all the operations must be contained in a transaction block. (See the documentation of the large object interface for more information.) Since @@ -1983,7 +1983,7 @@ testdb=> \set content '\'' `sed -e "s/'/\\\\\\'/g" < my_file.txt` '\' case you can escape a colon with a backslash to protect it from interpretation. (The colon syntax for variables is standard SQL for embedded query languages, such as ecpg. The colon syntax for - array slices and type casts are Postgres extensions, + array slices and type casts are PostgreSQL extensions, hence the conflict.) @@ -2168,7 +2168,7 @@ $endif If you have the readline library installed but psql - does not seem to use it, you must make sure that Postgres's + does not seem to use it, you must make sure that PostgreSQL's top-level configure script finds it. configure needs to find both the library libreadline.a (or a shared library equivalent) @@ -2202,7 +2202,7 @@ $ ./configure --with-includes=/opt/gnu/include --with-libs=/opt/gnu/lib ... This section only shows a few examples specific to psql. If you want to learn SQL or get familiar with - Postgres, you might wish to read the Tutorial that + PostgreSQL, you might wish to read the Tutorial that is included in the distribution. diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml index 67ba9a60116..bb443f8d465 100644 --- a/doc/src/sgml/ref/reindex.sgml +++ b/doc/src/sgml/ref/reindex.sgml @@ -1,6 +1,6 @@ @@ -147,7 +147,8 @@ REINDEX (Indeed, in this sort of scenario you may find that backends are crashing immediately at startup, due to reliance on the corrupted indexes.) To recover safely, the postmaster must be shut down and a - stand-alone Postgres backend must be started instead, giving it + stand-alone PostgreSQL backend must be + started instead, giving it the command-line options -O and -P (these options allow system table modifications and prevent use of system indexes, respectively). Then issue REINDEX INDEX, REINDEX TABLE, or diff --git a/doc/src/sgml/ref/reset.sgml b/doc/src/sgml/ref/reset.sgml index 59228cc819e..69c1f861ee6 100644 --- a/doc/src/sgml/ref/reset.sgml +++ b/doc/src/sgml/ref/reset.sgml @@ -1,6 +1,6 @@ @@ -92,7 +92,7 @@ RESET GEQO; Compatibility - RESET is a Postgres extension. + RESET is a PostgreSQL extension. diff --git a/doc/src/sgml/ref/revoke.sgml b/doc/src/sgml/ref/revoke.sgml index 7c00c36115b..6a858c5b3df 100644 --- a/doc/src/sgml/ref/revoke.sgml +++ b/doc/src/sgml/ref/revoke.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/rollback.sgml b/doc/src/sgml/ref/rollback.sgml index 527ea847493..2ba6eecc9c6 100644 --- a/doc/src/sgml/ref/rollback.sgml +++ b/doc/src/sgml/ref/rollback.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml index 3d45eff040e..ed080d35345 100644 --- a/doc/src/sgml/ref/select.sgml +++ b/doc/src/sgml/ref/select.sgml @@ -1,6 +1,6 @@ @@ -365,7 +365,7 @@ where from_item can be: from sub-tables (inheritance children) of the table. ONLY will suppress rows from sub-tables of the table. Before - Postgres 7.1, + PostgreSQL 7.1, this was the default result, and adding sub-tables was done by appending * to the table name. This old behaviour is available via the command @@ -776,7 +776,7 @@ SELECT name FROM distributors ORDER BY code; - As of Postgres 7.0, the + As of PostgreSQL 7.0, the query optimizer takes LIMIT into account when generating a query plan, so you are very likely to get different plans (yielding different row orders) depending on what you use for LIMIT and OFFSET. Thus, using @@ -942,7 +942,7 @@ SELECT actors.name -Postgres allows one to omit +PostgreSQL allows one to omit the FROM clause from a query. This feature was retained from the original PostQuel query language. It has a straightforward use to compute the results of simple constant @@ -983,7 +983,7 @@ rather than the unconstrained join SELECT distributors.* FROM distributors d, distributors distributors; that he will actually get. To help detect this sort of mistake, -Postgres 7.1 +PostgreSQL 7.1 and later will warn if the implicit-FROM feature is used in a query that also contains an explicit FROM clause. @@ -1011,7 +1011,7 @@ contains an explicit FROM clause. In the SQL92 standard, the optional keyword AS is just noise and can be omitted without affecting the meaning. - The Postgres parser requires this keyword when + The PostgreSQL parser requires this keyword when renaming output columns because the type extensibility features lead to parsing ambiguities in this context. AS is optional in FROM items, however. @@ -1025,10 +1025,10 @@ contains an explicit FROM clause. In SQL92, an ORDER BY clause may only use result column names or numbers, while a GROUP BY clause may only use input column names. - Postgres extends each of these clauses to + PostgreSQL extends each of these clauses to allow the other choice as well (but it uses the standard's interpretation if there is ambiguity). - Postgres also allows both clauses to specify + PostgreSQL also allows both clauses to specify arbitrary expressions. Note that names appearing in an expression will always be taken as input-column names, not as result-column names. @@ -1052,7 +1052,7 @@ contains an explicit FROM clause. The CORRESPONDING BY clause is not supported by - Postgres. + PostgreSQL. diff --git a/doc/src/sgml/ref/select_into.sgml b/doc/src/sgml/ref/select_into.sgml index 99c44024c84..8c8b6fc4483 100644 --- a/doc/src/sgml/ref/select_into.sgml +++ b/doc/src/sgml/ref/select_into.sgml @@ -1,6 +1,6 @@ @@ -148,7 +148,7 @@ where from_item can be: SQL92 uses SELECT ... INTO to represent selecting values into scalar variables of a host program, rather than creating a new table. This indeed is the usage found in PL/pgSQL and ecpg. - The Postgres usage of SELECT + The PostgreSQL usage of SELECT INTO to represent table creation is historical. It's best to use CREATE TABLE AS for this purpose in new code. (CREATE TABLE AS isn't standard either, but it's diff --git a/doc/src/sgml/ref/set.sgml b/doc/src/sgml/ref/set.sgml index 2b3e41a1c94..871a7a403a0 100644 --- a/doc/src/sgml/ref/set.sgml +++ b/doc/src/sgml/ref/set.sgml @@ -1,6 +1,6 @@ @@ -65,7 +65,7 @@ SET TIME ZONE { 'timezone' | LOCAL This option is only available if - Postgres is build with multibyte + PostgreSQL is build with multibyte support. @@ -106,10 +106,10 @@ SET TIME ZONE { 'timezone' | LOCAL - Postgres + PostgreSQL - Use traditional Postgres format. + Use traditional PostgreSQL format. @@ -127,7 +127,7 @@ SET TIME ZONE { 'timezone' | LOCAL The following two options determine both a substyle of the - SQL and Postgres output formats + SQL and PostgreSQL output formats and the preferred interpretation of ambiguous date input. @@ -225,7 +225,7 @@ SELECT setseed(value); This option is only available if - Postgres was built with multibyte + PostgreSQL was built with multibyte support. @@ -357,9 +357,10 @@ SELECT setseed(value); Examples - Set the style of date to traditional Postgres with European conventions: + Set the style of date to traditional + PostgreSQL with European conventions: -SET DATESTYLE TO Postgres,European; +SET DATESTYLE TO PostgreSQL,European; Set the time zone for Berkeley, California, using double quotes to @@ -402,7 +403,7 @@ SELECT CURRENT_TIMESTAMP AS today; attempts to mimic SQL92. However, SQL allows only numeric time zone offsets. All other parameter settings as well as the first syntax shown above are a - Postgres extension. + PostgreSQL extension. diff --git a/doc/src/sgml/ref/set_transaction.sgml b/doc/src/sgml/ref/set_transaction.sgml index 50af1e9b061..45bed289550 100644 --- a/doc/src/sgml/ref/set_transaction.sgml +++ b/doc/src/sgml/ref/set_transaction.sgml @@ -1,4 +1,4 @@ - + 2000-11-24 @@ -98,8 +98,9 @@ SET default_transaction_isolation = 'value' SERIALIZABLE is the default level in SQL. - Postgres does not provide the isolation levels and . Because + PostgreSQL does not provide the + isolation levels + and . Because of multi-version concurrency control, the serializable level is not truly serializable. See the User's Guide for details. @@ -109,7 +110,8 @@ SET default_transaction_isolation = 'value' In SQL there are two other transaction characteristics that can be set with these commands: whether the transaction is read-only and the size of the diagnostics area. - Neither of these concepts are supported in Postgres. + Neither of these concepts are supported in + PostgreSQL. diff --git a/doc/src/sgml/ref/show.sgml b/doc/src/sgml/ref/show.sgml index 93e4bb4aff7..a5e0d7735a9 100644 --- a/doc/src/sgml/ref/show.sgml +++ b/doc/src/sgml/ref/show.sgml @@ -1,6 +1,6 @@ @@ -120,7 +120,7 @@ NOTICE: geqo is on The SHOW command is a - Postgres extension. + PostgreSQL extension. diff --git a/doc/src/sgml/ref/truncate.sgml b/doc/src/sgml/ref/truncate.sgml index 6d413fd7adc..31ffd050c75 100644 --- a/doc/src/sgml/ref/truncate.sgml +++ b/doc/src/sgml/ref/truncate.sgml @@ -1,6 +1,6 @@ diff --git a/doc/src/sgml/ref/unlisten.sgml b/doc/src/sgml/ref/unlisten.sgml index 6d23fc76b6f..df0c4e1f948 100644 --- a/doc/src/sgml/ref/unlisten.sgml +++ b/doc/src/sgml/ref/unlisten.sgml @@ -1,6 +1,6 @@ @@ -93,7 +93,7 @@ UNLISTEN { notifyname | * } UNLISTEN is used to remove an existing NOTIFY registration. UNLISTEN cancels any existing registration of the current - Postgres session as a listener on the notify + PostgreSQL session as a listener on the notify condition notifyname. The special condition wildcard * cancels all listener registrations for the current session. diff --git a/doc/src/sgml/ref/update.sgml b/doc/src/sgml/ref/update.sgml index 76490428852..baf13a6ac87 100644 --- a/doc/src/sgml/ref/update.sgml +++ b/doc/src/sgml/ref/update.sgml @@ -1,6 +1,6 @@ @@ -64,7 +64,7 @@ UPDATE [ ONLY ] table SET fromlist - A Postgres + A PostgreSQL non-standard extension to allow columns from other tables to appear in the WHERE condition. diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml index 35394662f98..d1038735897 100644 --- a/doc/src/sgml/ref/vacuum.sgml +++ b/doc/src/sgml/ref/vacuum.sgml @@ -1,6 +1,6 @@ @@ -163,7 +163,7 @@ NOTICE: Index index: Pages 28; VACUUM reclaims storage occupied by deleted tuples. - In normal Postgres operation, tuples that + In normal PostgreSQL operation, tuples that are DELETEd or obsoleted by UPDATE are not physically removed from their table; they remain present until a VACUUM is done. Therefore it's necessary to do VACUUM @@ -226,7 +226,7 @@ NOTICE: Index index: Pages 28; ANALYZE command for the affected table. This will update the system catalogs with the results of all recent changes, and allow the - Postgres query optimizer to make better + PostgreSQL query optimizer to make better choices in planning user queries. diff --git a/doc/src/sgml/ref/vacuumdb.sgml b/doc/src/sgml/ref/vacuumdb.sgml index 487401b1e1e..57420d6f518 100644 --- a/doc/src/sgml/ref/vacuumdb.sgml +++ b/doc/src/sgml/ref/vacuumdb.sgml @@ -1,6 +1,6 @@ -- cgit v1.2.3