diff --git a/doc/src/sgml/ref/alter_domain.sgml b/doc/src/sgml/ref/alter_domain.sgml
index 08a26636acd2fe0febb21f0795571c8fb8cf04f3..1111da12f8e333ac76c3ef04219e94c3250e08ce 100644
--- a/doc/src/sgml/ref/alter_domain.sgml
+++ b/doc/src/sgml/ref/alter_domain.sgml
@@ -1,5 +1,5 @@
@@ -64,7 +64,7 @@ ALTER DOMAIN name
These forms change whether a domain is marked to allow NULL
- values or to reject NULL values. You may only SET NOT NULL>
+ values or to reject NULL values. You can only SET NOT NULL>
when the columns using the domain contain no null values.
diff --git a/doc/src/sgml/ref/alter_index.sgml b/doc/src/sgml/ref/alter_index.sgml
index a55bafb593565847ea5f8d957d6b391360f5ef30..813235fd6023a2e238230d768ef712d6b9b20e32 100644
--- a/doc/src/sgml/ref/alter_index.sgml
+++ b/doc/src/sgml/ref/alter_index.sgml
@@ -1,5 +1,5 @@
@@ -67,7 +67,7 @@ ALTER INDEX name RESET (
for details on the available parameters. Note that the index contents
will not be modified immediately by this command; depending on the
- parameter you may need to rebuild the index with
+ parameter you might need to rebuild the index with
to get the desired effects.
@@ -80,7 +80,7 @@ ALTER INDEX name RESET (
This form resets one or more index-method-specific storage parameters to
their defaults. As with SET>, a REINDEX
- may be needed to update the index entirely.
+ might be needed to update the index entirely.
diff --git a/doc/src/sgml/ref/alter_opfamily.sgml b/doc/src/sgml/ref/alter_opfamily.sgml
index 09906488e942290f31cfd020edb6c5fa1fd2ddf0..31d77fcf0c8a1093ea0d429531fac464779a71f0 100644
--- a/doc/src/sgml/ref/alter_opfamily.sgml
+++ b/doc/src/sgml/ref/alter_opfamily.sgml
@@ -1,5 +1,5 @@
@@ -202,7 +202,7 @@ ALTER OPERATOR FAMILY name USING DROP FUNCTION> the type(s) to specify
are the input data type(s) the function is intended to support; for
- GIN and GiST indexes this may have nothing to do with the actual input
+ GIN and GiST indexes this might have nothing to do with the actual input
argument types of the function.
diff --git a/doc/src/sgml/ref/alter_sequence.sgml b/doc/src/sgml/ref/alter_sequence.sgml
index c21201397bd6c7f596e3bd6d4afdd26494647b05..37c2ceb6314c8db13a6c39473fd4be47dd354727 100644
--- a/doc/src/sgml/ref/alter_sequence.sgml
+++ b/doc/src/sgml/ref/alter_sequence.sgml
@@ -1,5 +1,5 @@
@@ -136,7 +136,7 @@ ALTER SEQUENCE name SET SCHEMA CYCLE
- The optional CYCLE key word may be used to enable
+ The optional CYCLE key word can be used to enable
the sequence to wrap around when the
maxvalue or
minvalue has been
diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index d26f41e8f19dcfdb4044e6354cef6802d90b94f5..72f78a4074ca7a50b500e9a7e9160b4250c48765 100644
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -1,5 +1,5 @@
@@ -110,7 +110,7 @@ where action is one of:
These forms set or remove the default value for a column.
The default values only apply to subsequent INSERT
commands; they do not cause rows already in the table to change.
- Defaults may also be created for views, in which case they are
+ Defaults can also be created for views, in which case they are
inserted into INSERT> statements on the view before
the view's ON INSERT rule is applied.
@@ -200,7 +200,7 @@ where action is one of:
A disabled trigger is still known to the system, but is not executed
when its triggering event occurs. For a deferred trigger, the enable
status is checked when the event occurs, not when the trigger function
- is actually executed. One may disable or enable a single
+ is actually executed. One can disable or enable a single
trigger specified by name, or all triggers on the table, or only
user triggers (this option excludes triggers that are used to implement
foreign key constraints). Disabling or enabling constraint triggers
@@ -261,7 +261,7 @@ where action is one of:
for details on the available parameters. Note that the table contents
will not be modified immediately by this command; depending on the
- parameter you may need to rewrite the table to get the desired effects.
+ parameter you might need to rewrite the table to get the desired effects.
That can be done with or one of the forms of ALTER
TABLE> that forces a table rewrite.
@@ -284,7 +284,7 @@ where action is one of:
This form resets one or more storage parameters to their
- defaults. As with SET>, a table rewrite may be
+ defaults. As with SET>, a table rewrite might be
needed to update the table entirely.
@@ -309,7 +309,7 @@ where action is one of:
CHECK constraints of the parent. Currently
UNIQUE, PRIMARY KEY, and
FOREIGN KEY constraints are not considered, but
- this may change in the future.
+ this might change in the future.
@@ -607,7 +607,7 @@ where action is one of:
Adding a column with a non-null default or changing the type of an
existing column will require the entire table to be rewritten. This
- may take a significant amount of time for a large table; and it will
+ might take a significant amount of time for a large table; and it will
temporarily require double the disk space.
@@ -656,7 +656,7 @@ ALTER TABLE table ALTER COLUMN anycol TYPE anytype;
expression is not applied to the column's default value (if any); the
result might not be a constant expression as required for a default.
This means that when there is no implicit or assignment cast from old to
- new type, ALTER TYPE> may fail to convert the default even
+ new type, ALTER TYPE> might fail to convert the default even
though a USING clause is supplied. In such cases,
drop the default with DROP DEFAULT>, perform the ALTER
TYPE>, and then use SET DEFAULT> to add a suitable new
diff --git a/doc/src/sgml/ref/analyze.sgml b/doc/src/sgml/ref/analyze.sgml
index 3742366edfdc05e56019adf552e5a669eb35441e..28c272179aaf03cadc97ae4ab47aa1604b4d9939 100644
--- a/doc/src/sgml/ref/analyze.sgml
+++ b/doc/src/sgml/ref/analyze.sgml
@@ -1,5 +1,5 @@
@@ -109,7 +109,7 @@ ANALYZE [ VERBOSE ] [ table [ (ANALYZE usually
include a list of some of the most common values in each column and
a histogram showing the approximate data distribution in each
- column. One or both of these may be omitted if
+ column. One or both of these can be omitted if
ANALYZE deems them uninteresting (for example,
in a unique-key column, there are no common values) or if the
column data type does not support the appropriate operators. There
@@ -123,7 +123,7 @@ ANALYZE [ VERBOSE ] [ table [ (ANALYZE is run,
- even if the actual table contents did not change. This may result
+ even if the actual table contents did not change. This might result
in small changes in the planner's estimated costs shown by
EXPLAIN. In rare situations, this
non-determinism will cause the query optimizer to choose a
@@ -146,7 +146,7 @@ ANALYZE [ VERBOSE ] [ table [ (ANALYZE and the amount of space occupied in
pg_statistic. In particular, setting the
statistics target to zero disables collection of statistics for
- that column. It may be useful to do that for columns that are
+ that column. It might be useful to do that for columns that are
never used as part of the WHERE>, GROUP BY>,
or ORDER BY> clauses of queries, since the planner will
have no use for statistics on such columns.
diff --git a/doc/src/sgml/ref/begin.sgml b/doc/src/sgml/ref/begin.sgml
index add1b710690c0c3e312475ea7bcb0de6d7516eb5..af9a864a2f72d8ce3e0c724afb87e2408d30605b 100644
--- a/doc/src/sgml/ref/begin.sgml
+++ b/doc/src/sgml/ref/begin.sgml
@@ -1,5 +1,5 @@
@@ -109,7 +109,7 @@ where transaction_mode is one of:
For reasons of backwards compatibility, the commas between successive
- transaction_modes may be
+ transaction_modes can be
omitted.
diff --git a/doc/src/sgml/ref/checkpoint.sgml b/doc/src/sgml/ref/checkpoint.sgml
index 6071b2a28fafb9b7f029ef56d527d704272d6f3f..72fe648fbf064549777944385a7522a46e26c286 100644
--- a/doc/src/sgml/ref/checkpoint.sgml
+++ b/doc/src/sgml/ref/checkpoint.sgml
@@ -1,4 +1,4 @@
-
+
@@ -42,7 +42,7 @@ CHECKPOINT
- Only superusers may call CHECKPOINT. The command is
+ Only superusers can call CHECKPOINT. The command is
not intended for use during normal operation.
diff --git a/doc/src/sgml/ref/cluster.sgml b/doc/src/sgml/ref/cluster.sgml
index 5a2000f7bef8fc0ccaed1624b228c6c7d0333c48..29bb4d8ba05e7960686b7b2751e3ac928d11e8bf 100644
--- a/doc/src/sgml/ref/cluster.sgml
+++ b/doc/src/sgml/ref/cluster.sgml
@@ -1,5 +1,5 @@
@@ -132,7 +132,7 @@ CLUSTER
Because the planner records statistics about the ordering of
tables, it is advisable to run on the newly clustered table.
- Otherwise, the planner may make poor choices of query plans.
+ Otherwise, the planner might make poor choices of query plans.
diff --git a/doc/src/sgml/ref/comment.sgml b/doc/src/sgml/ref/comment.sgml
index bc3ab8f26d87f82cb7d17af8acde1d2b6a56cf4a..733f75ab3b78e15da953ddc5441fc26e34b2503f 100644
--- a/doc/src/sgml/ref/comment.sgml
+++ b/doc/src/sgml/ref/comment.sgml
@@ -1,5 +1,5 @@
@@ -93,7 +93,7 @@ COMMENT ON
The name of the object to be commented. Names of tables,
aggregates, domains, functions, indexes, operators, operator classes,
- operator families, sequences, types, and views may be schema-qualified.
+ operator families, sequences, types, and views can be schema-qualified.
diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index 6eab13705fbc8276bc5f4763cd53e1f4aa3336ac..5d3bf5906751743341b70b12196dbef754b96130 100644
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -1,5 +1,5 @@
@@ -358,9 +358,9 @@ COPY count
should not lead to problems in the event of a COPY
TO, but the target table will already have received
earlier rows in a COPY FROM. These rows will not
- be visible or accessible, but they still occupy disk space. This may
+ be visible or accessible, but they still occupy disk space. This might
amount to a considerable amount of wasted disk space if the failure
- happened well into a large copy operation. You may wish to invoke
+ happened well into a large copy operation. You might wish to invoke
VACUUM to recover the wasted space.
@@ -395,7 +395,7 @@ COPY count
- Backslash characters (\>) may be used in the
+ Backslash characters (\>) can be used in the
COPY data to quote data characters that might
otherwise be taken as row or column delimiters. In particular, the
following characters must> be preceded by a backslash if
@@ -694,7 +694,7 @@ There is no alignment padding or any other extra data between fields.
Presently, all data values in a COPY BINARY file are
assumed to be in binary format (format code one). It is anticipated that a
-future extension may add a header field that allows per-column format codes
+future extension might add a header field that allows per-column format codes
to be specified.
diff --git a/doc/src/sgml/ref/create_aggregate.sgml b/doc/src/sgml/ref/create_aggregate.sgml
index aea0247d0dbf89c8e554fc663bba4642318e789d..6024a168587f99c824761a3f52076dafbbfe19a9 100644
--- a/doc/src/sgml/ref/create_aggregate.sgml
+++ b/doc/src/sgml/ref/create_aggregate.sgml
@@ -1,5 +1,5 @@
@@ -96,7 +96,7 @@ CREATE AGGREGATE name (
- An aggregate function may provide an initial condition,
+ An aggregate function can provide an initial condition,
that is, an initial value for the internal state value.
This is specified and stored in the database as a value of type
text, but it must be a valid external representation
diff --git a/doc/src/sgml/ref/create_cast.sgml b/doc/src/sgml/ref/create_cast.sgml
index e8f3e5fabdeafa4513ebdb411abeb95b0ad662e8..3e1c9f22a9cff5e7979ebdd3d137e790b39eb64c 100644
--- a/doc/src/sgml/ref/create_cast.sgml
+++ b/doc/src/sgml/ref/create_cast.sgml
@@ -1,4 +1,4 @@
-
+
@@ -44,7 +44,7 @@ SELECT CAST(42 AS text);
- Two types may be binary compatible, which
+ Two types can be binary compatible, which
means that they can be converted into one another for
free without invoking any function. This requires that
corresponding values use the same internal representation. For
@@ -145,7 +145,7 @@ SELECT 'The time is ' || CAST(now() AS text);
- The function used to perform the cast. The function name may
+ The function used to perform the cast. The function name can
be schema-qualified. If it is not, the function will be looked
up in the schema search path. The function's result data type must
match the target type of the cast. Its arguments are discussed below.
@@ -169,7 +169,7 @@ SELECT 'The time is ' || CAST(now() AS text);
- Indicates that the cast may be invoked implicitly in assignment
+ Indicates that the cast can be invoked implicitly in assignment
contexts.
@@ -180,14 +180,14 @@ SELECT 'The time is ' || CAST(now() AS text);
- Indicates that the cast may be invoked implicitly in any context.
+ Indicates that the cast can be invoked implicitly in any context.
- Cast implementation functions may have one to three arguments.
+ Cast implementation functions can have one to three arguments.
The first argument type must be identical to the cast's source type.
The second argument,
if present, must be type integer>; it receives the type
diff --git a/doc/src/sgml/ref/create_conversion.sgml b/doc/src/sgml/ref/create_conversion.sgml
index d5e8c47c1d9c5ca0081645571fc33befea1227a4..8454abbd21b3caf88aea83e898fcae3a56fa5646 100644
--- a/doc/src/sgml/ref/create_conversion.sgml
+++ b/doc/src/sgml/ref/create_conversion.sgml
@@ -1,4 +1,4 @@
-
+
@@ -27,7 +27,7 @@ CREATE [ DEFAULT ] CONVERSION nameCREATE CONVERSION defines a new conversion between
- character set encodings. Conversion names may be used in the
+ character set encodings. Conversion names can be used in the
convert function
to specify a particular encoding conversion. Also, conversions that
are marked DEFAULT> can be used for automatic encoding
@@ -65,7 +65,7 @@ CREATE [ DEFAULT ] CONVERSION name
- The name of the conversion. The conversion name may be
+ The name of the conversion. The conversion name can be
schema-qualified. If it is not, the conversion is defined in the
current schema. The conversion name must be unique within a
schema.
@@ -98,7 +98,7 @@ CREATE [ DEFAULT ] CONVERSION name
- The function used to perform the conversion. The function name may
+ The function used to perform the conversion. The function name can
be schema-qualified. If it is not, the function will be looked
up in the path.
@@ -129,7 +129,7 @@ conv_proc(
- The privileges required to create a conversion may be changed in a future
+ The privileges required to create a conversion might be changed in a future
release.
diff --git a/doc/src/sgml/ref/create_database.sgml b/doc/src/sgml/ref/create_database.sgml
index 3183e2a359a7b9bd2031bbd4da4083665bd2677c..d4301a73f6a97330094df858b491fb7373376668 100644
--- a/doc/src/sgml/ref/create_database.sgml
+++ b/doc/src/sgml/ref/create_database.sgml
@@ -1,5 +1,5 @@
@@ -60,7 +60,7 @@ CREATE DATABASE name
database containing only the standard objects predefined by your
version of PostgreSQL. This is useful
if you wish to avoid copying
- any installation-local objects that may have been added to
+ any installation-local objects that might have been added to
template1>.
diff --git a/doc/src/sgml/ref/create_domain.sgml b/doc/src/sgml/ref/create_domain.sgml
index 70d75c662f59c9366c926431541ba9eb17d015f9..7cd698f83d2b4e54e2a365697b7ae6cc90892511 100644
--- a/doc/src/sgml/ref/create_domain.sgml
+++ b/doc/src/sgml/ref/create_domain.sgml
@@ -1,5 +1,5 @@
@@ -76,7 +76,7 @@ where constraint is:
data_type
- The underlying data type of the domain. This may include array
+ The underlying data type of the domain. This can include array
specifiers.
diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml
index 5309059de3052e6ec40a2f458cd2df10fb839368..9e26248d427efa98021ddfb9332ea6510873c97b 100644
--- a/doc/src/sgml/ref/create_function.sgml
+++ b/doc/src/sgml/ref/create_function.sgml
@@ -1,5 +1,5 @@
@@ -49,7 +49,7 @@ CREATE [ OR REPLACE ] FUNCTION
specified schema. Otherwise it is created in the current schema.
The name of the new function must not match any existing function
with the same argument types in the same schema. However,
- functions of different argument types may share a name (this is
+ functions of different argument types can share a name (this is
called overloading>).
@@ -125,11 +125,11 @@ CREATE [ OR REPLACE ] FUNCTION
The data type(s) of the function's arguments (optionally
- schema-qualified), if any. The argument types may be base, composite,
- or domain types, or may reference the type of a table column.
+ schema-qualified), if any. The argument types can be base, composite,
+ or domain types, or can reference the type of a table column.
- Depending on the implementation language it may also be allowed
+ Depending on the implementation language it might also be allowed
to specify pseudotypes> such as cstring>.
Pseudotypes indicate that the actual argument type is either
incompletely specified, or outside the set of ordinary SQL data types.
@@ -151,16 +151,16 @@ CREATE [ OR REPLACE ] FUNCTION
The return data type (optionally schema-qualified). The return type
- may be a base, composite, or domain type,
- or may reference the type of a table column.
- Depending on the implementation language it may also be allowed
+ can be a base, composite, or domain type,
+ or can reference the type of a table column.
+ Depending on the implementation language it might also be allowed
to specify pseudotypes> such as cstring>.
If the function is not supposed to return a value, specify
void> as the return type.
When there are OUT> or INOUT> parameters,
- the RETURNS> clause may be omitted. If present, it
+ the RETURNS> clause can be omitted. If present, it
must agree with the result type implied by the output parameters:
RECORD> if there are multiple output parameters, or
the same type as the single output parameter.
@@ -185,10 +185,10 @@ CREATE [ OR REPLACE ] FUNCTION
The name of the language that the function is implemented in.
- May be SQL, C,
+ Can be SQL, C,
internal, or the name of a user-defined
procedural language. For backward compatibility,
- the name may be enclosed by single quotes.
+ the name can be enclosed by single quotes.
@@ -202,7 +202,7 @@ CREATE [ OR REPLACE ] FUNCTION
These attributes inform the query optimizer about the behavior
of the function. At most one choice
- may be specified. If none of these appear,
+ can be specified. If none of these appear,
VOLATILE is the default assumption.
@@ -326,7 +326,7 @@ CREATE [ OR REPLACE ] FUNCTION
A string constant defining the function; the meaning depends on the
- language. It may be an internal function name, the path to an
+ language. It can be an internal function name, the path to an
object file, an SQL command, or text in a procedural language.
@@ -357,7 +357,7 @@ CREATE [ OR REPLACE ] FUNCTION
The historical way to specify optional pieces of information
- about the function. The following attributes may appear here:
+ about the function. The following attributes can appear here:
diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index d64901d2e98189e4ad9a46da0cb03cb87d2e7a53..db873c720774e0955ffac8871b9c28e7c76ba408 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -1,5 +1,5 @@
@@ -75,7 +75,7 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] name
- The expression used in the WHERE clause may refer
+ The expression used in the WHERE clause can refer
only to columns of the underlying table, but it can use all columns,
not just the ones being indexed. Presently, subqueries and
aggregate expressions are also forbidden in WHERE.
@@ -172,7 +172,7 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] name
An expression based on one or more columns of the table. The
expression usually must be written with surrounding parentheses,
- as shown in the syntax. However, the parentheses may be omitted
+ as shown in the syntax. However, the parentheses can be omitted
if the expression has the form of a function call.
@@ -324,14 +324,14 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] name
If a problem arises during the second scan of the table, such as a
uniqueness violation in a unique index, the CREATE INDEX>
command will fail but leave behind an invalid> index. This index
- will be ignored for querying purposes because it may be incomplete;
+ will be ignored for querying purposes because it might be incomplete;
however it will still consume update overhead. The recommended recovery
method in such cases is to drop the index and try again to perform
CREATE INDEX CONCURRENTLY>. (Another possibility is to rebuild
@@ -378,7 +378,7 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] name
Currently, only the B-tree and GiST index methods support
- multicolumn indexes. Up to 32 fields may be specified by default.
+ multicolumn indexes. Up to 32 fields can be specified by default.
(This limit can be altered when building
PostgreSQL.) Only B-tree currently
supports unique indexes.
diff --git a/doc/src/sgml/ref/create_language.sgml b/doc/src/sgml/ref/create_language.sgml
index 485cbe3df8397ea9cdd7a973cb2fe96bfd7d03cb..b09b38bee99c4ab6c92fe61c692bf2a840eb4bc5 100644
--- a/doc/src/sgml/ref/create_language.sgml
+++ b/doc/src/sgml/ref/create_language.sgml
@@ -1,5 +1,5 @@
@@ -107,7 +107,7 @@ CREATE [ TRUSTED ] [ PROCEDURAL ] LANGUAGE name
- For backward compatibility, the name may be enclosed by single
+ For backward compatibility, the name can be enclosed by single
quotes.
@@ -192,7 +192,7 @@ CREATE [ TRUSTED ] [ PROCEDURAL ] LANGUAGE name
To create functions in a procedural language, a user must have the
USAGE privilege for the language. By default,
USAGE> is granted to PUBLIC> (i.e., everyone)
- for trusted languages. This may be revoked if desired.
+ for trusted languages. This can be revoked if desired.
@@ -208,7 +208,7 @@ CREATE [ TRUSTED ] [ PROCEDURAL ] LANGUAGE name
in pg_pltemplate>. But when there is an entry,
the functions need not already exist;
they will be automatically defined if not present in the database.
- (This can result in CREATE LANGUAGE> failing, if the
+ (This might result in CREATE LANGUAGE> failing, if the
shared library that implements the language is not available in
the installation.)
diff --git a/doc/src/sgml/ref/create_opclass.sgml b/doc/src/sgml/ref/create_opclass.sgml
index 85a31e3b19500fe8fcb8f91363e07e313c3670be..78276ec954d5a118aa994d1b7d2b9da2f8f5ebbd 100644
--- a/doc/src/sgml/ref/create_opclass.sgml
+++ b/doc/src/sgml/ref/create_opclass.sgml
@@ -1,5 +1,5 @@
@@ -88,7 +88,7 @@ CREATE OPERATOR CLASS name [ DEFAUL
name
- The name of the operator class to be created. The name may be
+ The name of the operator class to be created. The name can be
schema-qualified.
@@ -161,7 +161,7 @@ CREATE OPERATOR CLASS name [ DEFAUL
In an OPERATOR> clause,
the operand data type(s) of the operator, or NONE> to
signify a left-unary or right-unary operator. The operand data
- types may be omitted in the normal case where they are the same
+ types can be omitted in the normal case where they are the same
as the operator class's data type.
@@ -236,7 +236,7 @@ CREATE OPERATOR CLASS name [ DEFAUL
The OPERATOR>, FUNCTION>, and STORAGE>
- clauses may appear in any order.
+ clauses can appear in any order.
diff --git a/doc/src/sgml/ref/create_operator.sgml b/doc/src/sgml/ref/create_operator.sgml
index 955d9dbb2d1b685cbc870b3c7f972478997e392b..0b53540b0df2a972bf92efdad87afa38017de5ed 100644
--- a/doc/src/sgml/ref/create_operator.sgml
+++ b/doc/src/sgml/ref/create_operator.sgml
@@ -1,5 +1,5 @@
@@ -108,7 +108,7 @@ CREATE OPERATOR name (
The name of the operator to be defined. See above for allowable
- characters. The name may be schema-qualified, for example
+ characters. The name can be schema-qualified, for example
CREATE OPERATOR myschema.+ (...)>. If not, then
the operator is created in the current schema. Two operators
in the same schema can have the same name if they operate on
diff --git a/doc/src/sgml/ref/create_opfamily.sgml b/doc/src/sgml/ref/create_opfamily.sgml
index d8ddb683b9e9be1635b731b179a3f39c16733b14..ee40196a473eeec72e344e0f8805782af63cd08d 100644
--- a/doc/src/sgml/ref/create_opfamily.sgml
+++ b/doc/src/sgml/ref/create_opfamily.sgml
@@ -1,5 +1,5 @@
@@ -83,7 +83,7 @@ CREATE OPERATOR FAMILY name USING <
name
- The name of the operator family to be created. The name may be
+ The name of the operator family to be created. The name can be
schema-qualified.
diff --git a/doc/src/sgml/ref/create_role.sgml b/doc/src/sgml/ref/create_role.sgml
index c1b4a666249fd17417e8a38bf8a56ed625073622..1ad27d221ce08f8819e9f5add5b980b85a5eea52 100644
--- a/doc/src/sgml/ref/create_role.sgml
+++ b/doc/src/sgml/ref/create_role.sgml
@@ -1,5 +1,5 @@
@@ -217,7 +217,7 @@ where option can be:
- Note that older clients may lack support for the MD5
+ Note that older clients might lack support for the MD5
authentication mechanism that is needed to work with passwords
that are stored encrypted.
diff --git a/doc/src/sgml/ref/create_rule.sgml b/doc/src/sgml/ref/create_rule.sgml
index 2822e920254077301c4b08661484109067d03437..446dad1856356a2e28e1d2e984b4b3b7b55aef51 100644
--- a/doc/src/sgml/ref/create_rule.sgml
+++ b/doc/src/sgml/ref/create_rule.sgml
@@ -1,5 +1,5 @@
@@ -136,9 +136,9 @@ CREATE [ OR REPLACE ] RULE name AS
Any SQL conditional expression (returning
- boolean). The condition expression may not refer
+ boolean). The condition expression cannot refer
to any tables except NEW> and OLD>, and
- may not contain aggregate functions.
+ can not contain aggregate functions.
@@ -186,7 +186,7 @@ CREATE [ OR REPLACE ] RULE name AS
Within condition and
command, the special
- table names NEW and OLD may
+ table names NEW and OLD can
be used to refer to values in the referenced table.
NEW is valid in ON INSERT and
ON UPDATE rules to refer to the new row being
@@ -257,7 +257,7 @@ UPDATE mytable SET name = 'foo' WHERE id = 42;
one NOTIFY event will be sent during the
UPDATE, whether or not there are any rows that
match the condition id = 42. This is an
- implementation restriction that may be fixed in future releases.
+ implementation restriction that might be fixed in future releases.
diff --git a/doc/src/sgml/ref/create_schema.sgml b/doc/src/sgml/ref/create_schema.sgml
index 329d80406f17e33e5b896819402f46d1ff72c695..0f39b840437054e2e6f4642c08654537d013ae7b 100644
--- a/doc/src/sgml/ref/create_schema.sgml
+++ b/doc/src/sgml/ref/create_schema.sgml
@@ -1,5 +1,5 @@
@@ -38,7 +38,7 @@ CREATE SCHEMA AUTHORIZATION username
A schema is essentially a namespace:
it contains named objects (tables, data types, functions, and operators)
- whose names may duplicate those of other objects existing in other
+ whose names can duplicate those of other objects existing in other
schemas. Named objects are accessed either by qualifying>
their names with the schema name as a prefix, or by setting a search
path that includes the desired schema(s). A CREATE> command
@@ -78,7 +78,7 @@ CREATE SCHEMA AUTHORIZATION username
The name of the user who will own the schema. If omitted,
defaults to the user executing the command. Only superusers
- may create schemas owned by users other than themselves.
+ can create schemas owned by users other than themselves.
@@ -163,9 +163,9 @@ CREATE VIEW hollywood.winners AS
The SQL standard specifies that the subcommands in CREATE
- SCHEMA may appear in any order. The present
+ SCHEMA can appear in any order. The present
PostgreSQL implementation does not
- handle all cases of forward references in subcommands; it may
+ handle all cases of forward references in subcommands; it might
sometimes be necessary to reorder the subcommands in order to avoid
forward references.
diff --git a/doc/src/sgml/ref/create_sequence.sgml b/doc/src/sgml/ref/create_sequence.sgml
index f24610d1e43d2a6cdfa51d18966c9d0bef9800fb..bd3c4ac86996d8dd63be3220bfe567db6a677e45 100644
--- a/doc/src/sgml/ref/create_sequence.sgml
+++ b/doc/src/sgml/ref/create_sequence.sgml
@@ -1,5 +1,5 @@
@@ -41,7 +41,7 @@ CREATE [ TEMPORARY | TEMP ] SEQUENCE name
If a schema name is given then the sequence is created in the
specified schema. Otherwise it is created in the current schema.
- Temporary sequences exist in a special schema, so a schema name may not be
+ Temporary sequences exist in a special schema, so a schema name cannot be
given when creating a temporary sequence.
The sequence name must be distinct from the name of any other sequence,
table, index, or view in the same schema.
@@ -65,7 +65,7 @@ SELECT * FROM name;
to examine the parameters and current state of a sequence. In particular,
the last_value> field of the sequence shows the last value
- allocated by any session. (Of course, this value may be obsolete
+ allocated by any session. (Of course, this value might be obsolete
by the time it's printed, if other sessions are actively doing
nextval> calls.)
@@ -224,13 +224,13 @@ SELECT * FROM name;
Sequences are based on bigint> arithmetic, so the range
cannot exceed the range of an eight-byte integer
(-9223372036854775808 to 9223372036854775807). On some older
- platforms, there may be no compiler support for eight-byte
+ platforms, there might be no compiler support for eight-byte
integers, in which case sequences use regular integer>
arithmetic (range -2147483648 to +2147483647).
- Unexpected results may be obtained if a cache setting greater than one is
used for a sequence object that will be used concurrently by
multiple sessions. Each session will allocate and cache successive
@@ -246,7 +246,7 @@ SELECT * FROM name;
Furthermore, although multiple sessions are guaranteed to allocate
- distinct sequence values, the values may be generated out of
+ distinct sequence values, the values might be generated out of
sequence when all the sessions are considered. For example, with
a cache setting of 10,
session A might reserve values 1..10 and return
diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml
index 77b6275ce5eeaf8477f8fa1c78adccbbd4e54edf..ef1b1466c472462ac797a7574d99028edeb93a4d 100644
--- a/doc/src/sgml/ref/create_table.sgml
+++ b/doc/src/sgml/ref/create_table.sgml
@@ -1,5 +1,5 @@
@@ -74,7 +74,7 @@ and table_constraint is:
If a schema name is given (for example, CREATE TABLE
myschema.mytable ...>) then the table is created in the specified
schema. Otherwise it is created in the current schema. Temporary
- tables exist in a special schema, so a schema name may not be given
+ tables exist in a special schema, so a schema name cannot be given
when creating a temporary table. The name of the table must be
distinct from the name of any other table, sequence, index, or view
in the same schema.
@@ -156,7 +156,7 @@ and table_constraint is:
data_type
- The data type of the column. This may include array
+ The data type of the column. This can include array
specifiers. For more information on the data types supported by
PostgreSQL, refer to .
@@ -319,7 +319,7 @@ and table_constraint is:
The UNIQUE constraint specifies that a
- group of one or more columns of a table may contain
+ group of one or more columns of a table can contain
only unique values. The behavior of the unique table constraint
is the same as that for column constraints, with the additional
capability to span multiple columns.
@@ -345,13 +345,13 @@ and table_constraint is:
The primary key constraint specifies that a column or columns of a table
- may contain only unique (non-duplicate), nonnull values.
+ can contain only unique (non-duplicate), nonnull values.
Technically, PRIMARY KEY is merely a
combination of UNIQUE> and NOT NULL>, but
identifying a set of columns as primary key also provides
metadata about the design of the schema, as a primary key
implies that other tables
- may rely on this set of columns as a unique identifier for rows.
+ can rely on this set of columns as a unique identifier for rows.
@@ -379,7 +379,7 @@ and table_constraint is:
raised and the insert or update does not alter the database. A
check constraint specified as a column constraint should
reference that column's value only, while an expression
- appearing in a table constraint may reference multiple columns.
+ appearing in a table constraint can reference multiple columns.
@@ -412,7 +412,7 @@ and table_constraint is:
class="parameter">reftable is used. The
referenced columns must be the columns of a unique or primary
key constraint in the referenced table. Note that foreign key
- constraints may not be defined between temporary tables and
+ constraints cannot be defined between temporary tables and
permanent tables.
@@ -501,7 +501,7 @@ and table_constraint is:
- If the referenced column(s) are changed frequently, it may be wise to
+ If the referenced column(s) are changed frequently, it might be wise to
add an index to the foreign key column so that referential actions
associated with the foreign key column can be performed more
efficiently.
@@ -517,7 +517,7 @@ and table_constraint is:
This controls whether the constraint can be deferred. A
constraint that is not deferrable will be checked immediately
after every command. Checking of constraints that are
- deferrable may be postponed until the end of the transaction
+ deferrable can be postponed until the end of the transaction
(using the command).
NOT DEFERRABLE is the default. Only foreign
key constraints currently accept this clause. All other
@@ -1005,8 +1005,8 @@ CREATE TABLE cinemas (
The SQL standard says that CHECK> column constraints
- may only refer to the column they apply to; only CHECK>
- table constraints may refer to multiple columns.
+ can only refer to the column they apply to; only CHECK>
+ table constraints can refer to multiple columns.
PostgreSQL does not enforce this
restriction; it treats column and table check constraints alike.
diff --git a/doc/src/sgml/ref/create_tablespace.sgml b/doc/src/sgml/ref/create_tablespace.sgml
index 797591d613a8b8920f018aa3aa844311a9452ef8..4b75ba12e664cc83a99841012580b7379dec74e4 100644
--- a/doc/src/sgml/ref/create_tablespace.sgml
+++ b/doc/src/sgml/ref/create_tablespace.sgml
@@ -1,5 +1,5 @@
@@ -36,7 +36,7 @@ CREATE TABLESPACE tablespacename [
A tablespace allows superusers to define an alternative location on
the file system where the data files containing database objects
- (such as tables and indexes) may reside.
+ (such as tables and indexes) can reside.
@@ -69,7 +69,7 @@ CREATE TABLESPACE tablespacename [
The name of the user who will own the tablespace. If omitted,
defaults to the user executing the command. Only superusers
- may create tablespaces, but they can assign ownership of tablespaces
+ can create tablespaces, but they can assign ownership of tablespaces
to non-superusers.
diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml
index fcbe444574b1654d05249f4113878431e73e7fbd..329bee7c5e3cde182de461e6c3cacb912e427b8b 100644
--- a/doc/src/sgml/ref/create_trigger.sgml
+++ b/doc/src/sgml/ref/create_trigger.sgml
@@ -1,5 +1,5 @@
@@ -44,7 +44,7 @@ CREATE TRIGGER name { BEFORE | AFTE
completed (after constraints are checked and the
INSERT, UPDATE, or
DELETE has completed). If the trigger fires
- before the event, the trigger may skip the operation for the
+ before the event, the trigger can skip the operation for the
current row, or change the row being inserted (for
INSERT and UPDATE operations
only). If the trigger fires after the event, all changes, including
@@ -160,10 +160,10 @@ CREATE TRIGGER name { BEFORE | AFTE
An optional comma-separated list of arguments to be provided to
the function when the trigger is executed. The arguments are
literal string constants. Simple names and numeric constants
- may be written here, too, but they will all be converted to
+ can be written here, too, but they will all be converted to
strings. Please check the description of the implementation
language of the trigger function about how the trigger arguments
- are accessible within the function; it may be different from
+ are accessible within the function; it might be different from
normal function arguments.
diff --git a/doc/src/sgml/ref/create_type.sgml b/doc/src/sgml/ref/create_type.sgml
index 2f1f6eab3c415d1c15cb5f26c639efe016e461b4..7736b87362d9f8d0fc2894650b592b39db5e12d6 100644
--- a/doc/src/sgml/ref/create_type.sgml
+++ b/doc/src/sgml/ref/create_type.sgml
@@ -1,5 +1,5 @@
@@ -82,7 +82,7 @@ CREATE TYPE name
The second form of CREATE TYPE creates a new base type
- (scalar type). The parameters may appear in any order, not only that
+ (scalar type). The parameters can appear in any order, not only that
illustrated above, and most are optional. You must register
two or more functions (using CREATE FUNCTION) before
defining the type. The support functions
@@ -103,7 +103,7 @@ CREATE TYPE name
converts the type's external textual representation to the internal
representation used by the operators and functions defined for the type.
output_function
- performs the reverse transformation. The input function may be
+ performs the reverse transformation. The input function can be
declared as taking one argument of type cstring,
or as taking three arguments of types
cstring, oid, integer.
@@ -118,7 +118,7 @@ CREATE TYPE name
input value. The function must still return NULL in this case, unless
it raises an error.
(This case is mainly meant to support domain input functions, which
- may need to reject NULL inputs.)
+ might need to reject NULL inputs.)
The output function must be
declared as taking one argument of the new data type.
The output function must return type cstring.
@@ -136,7 +136,7 @@ CREATE TYPE name
representation is in the machine's native byte order.) The receive
function should perform adequate checking to ensure that the value is
valid.
- The receive function may be declared as taking one argument of type
+ The receive function can be declared as taking one argument of type
internal, or as taking three arguments of types
internal, oid, integer.
The first argument is a pointer to a StringInfo buffer
@@ -148,7 +148,7 @@ CREATE TYPE name
input value. The function must still return NULL in this case, unless
it raises an error.
(This case is mainly meant to support domain receive functions, which
- may need to reject NULL inputs.)
+ might need to reject NULL inputs.)
Similarly, the optional
send_function converts
from the internal representation to the external binary representation.
@@ -234,7 +234,7 @@ CREATE TYPE name
The optional flag PASSEDBYVALUE indicates that
values of this data type are passed by value, rather than by
- reference. You may not pass by value types whose internal
+ reference. You cannot pass by value types whose internal
representation is larger than the size of the Datum> type
(4 bytes on most machines, 8 bytes on a few).
@@ -260,17 +260,17 @@ CREATE TYPE name
main table, but the system will not try to compress it.
main allows compression, but discourages moving
the value out of the main table. (Data items with this storage
- strategy may still be moved out of the main table if there is no
+ strategy might still be moved out of the main table if there is no
other way to make a row fit, but they will be kept in the main
table preferentially over extended and
external items.)
- A default value may be specified, in case a user wants columns of the
+ A default value can be specified, in case a user wants columns of the
data type to default to something other than the null value.
Specify the default with the DEFAULT key word.
- (Such a default may be overridden by an explicit DEFAULT
+ (Such a default can be overridden by an explicit DEFAULT
clause attached to a particular column.)
@@ -531,7 +531,7 @@ CREATE TYPE name
the name of the new data type as the return type of the input function.
The shell type is implicitly created in this situation, and then it
can be referenced in the definitions of the remaining I/O functions.
- This approach still works, but is deprecated and may be disallowed in
+ This approach still works, but is deprecated and might be disallowed in
some future release. Also, to avoid accidentally cluttering
the catalogs with shell types as a result of simple typos in function
definitions, a shell type will only be made this way when the input
diff --git a/doc/src/sgml/ref/create_view.sgml b/doc/src/sgml/ref/create_view.sgml
index f6e75ce3e2a0ef9bebaaa2e3bb03bfec0480ef59..dc160818c3f51894545ae6dbda671231ada7a13e 100644
--- a/doc/src/sgml/ref/create_view.sgml
+++ b/doc/src/sgml/ref/create_view.sgml
@@ -1,5 +1,5 @@
@@ -45,7 +45,7 @@ CREATE [ OR REPLACE ] [ TEMP | TEMPORARY ] VIEW n
If a schema name is given (for example, CREATE VIEW
myschema.myview ...>) then the view is created in the specified
schema. Otherwise it is created in the current schema. Temporary
- views exist in a special schema, so a schema name may not be given
+ views exist in a special schema, so a schema name cannot be given
when creating a temporary view. The name of the view must be
distinct from the name of any other view, table, sequence, or index
in the same schema.
diff --git a/doc/src/sgml/ref/declare.sgml b/doc/src/sgml/ref/declare.sgml
index 30f924268c56d35ee336a826d2ab554b9d1bccb1..4afe2d03b255ec3f1f2fa2605bc1eb158893e053 100644
--- a/doc/src/sgml/ref/declare.sgml
+++ b/doc/src/sgml/ref/declare.sgml
@@ -1,5 +1,5 @@
@@ -47,10 +47,10 @@ DECLARE name [ BINARY ] [ INSENSITI
SELECT> would produce. Since data is stored natively in
binary format, the system must do a conversion to produce the text
format. Once the information comes back in text form, the client
- application may need to convert it to a binary format to manipulate
+ application might need to convert it to a binary format to manipulate
it. In addition, data in the text format is often larger in size
than in the binary format. Binary cursors return the data in a
- binary representation that may be more easily manipulated.
+ binary representation that might be more easily manipulated.
Nevertheless, if you intend to display the data as text anyway,
retrieving it in text form will
save you some effort on the client side.
@@ -123,10 +123,10 @@ DECLARE name [ BINARY ] [ INSENSITI
NO SCROLL
- SCROLL specifies that the cursor may be used
+ SCROLL specifies that the cursor can be used
to retrieve rows in a nonsequential fashion (e.g.,
backward). Depending upon the complexity of the query's
- execution plan, specifying SCROLL may impose
+ execution plan, specifying SCROLL might impose
a performance penalty on the query's execution time.
NO SCROLL specifies that the cursor cannot be
used to retrieve rows in a nonsequential fashion. The default is to
@@ -142,7 +142,7 @@ DECLARE name [ BINARY ] [ INSENSITI
WITHOUT HOLD
- WITH HOLD specifies that the cursor may
+ WITH HOLD specifies that the cursor can
continue to be used after the transaction that created it
successfully commits. WITHOUT HOLD specifies
that the cursor cannot be used outside of the transaction that
@@ -195,7 +195,7 @@ DECLARE name [ BINARY ] [ INSENSITI
The key words BINARY,
- INSENSITIVE, and SCROLL may
+ INSENSITIVE, and SCROLL can
appear in any order.
diff --git a/doc/src/sgml/ref/delete.sgml b/doc/src/sgml/ref/delete.sgml
index 3d7aba8af5536f9dfe389cca34ade1306b66654d..17e1e8b9c737ebcac9f7e2aa9fe1fdee15a373eb 100644
--- a/doc/src/sgml/ref/delete.sgml
+++ b/doc/src/sgml/ref/delete.sgml
@@ -1,5 +1,5 @@
@@ -146,7 +146,7 @@ DELETE FROM [ ONLY ] table [ [ AS ]
An expression to be computed and returned by the DELETE>
- command after each row is deleted. The expression may use any
+ command after each row is deleted. The expression can use any
column names of the table
or table(s) listed in USING>.
Write *> to return all columns.
@@ -197,7 +197,7 @@ DELETE countPostgreSQL lets you reference columns of
other tables in the WHERE> condition by specifying the
other tables in the USING clause. For example,
- to delete all films produced by a given producer, one might do
+ to delete all films produced by a given producer, one can do
DELETE FROM films USING producers
WHERE producer_id = producers.id AND producers.name = 'foo';
diff --git a/doc/src/sgml/ref/drop_conversion.sgml b/doc/src/sgml/ref/drop_conversion.sgml
index f12a445018591755df373c4aa87a3592fcad6167..2ff6f64b01301216698fa44e9de3aab88bab9bdb 100644
--- a/doc/src/sgml/ref/drop_conversion.sgml
+++ b/doc/src/sgml/ref/drop_conversion.sgml
@@ -1,4 +1,4 @@
-
+
@@ -49,7 +49,7 @@ DROP CONVERSION [ IF EXISTS ] name [ CASCADE | RESTRI
- The name of the conversion. The conversion name may be
+ The name of the conversion. The conversion name can be
schema-qualified.
diff --git a/doc/src/sgml/ref/drop_function.sgml b/doc/src/sgml/ref/drop_function.sgml
index 98a41244170920d100a110e4cffe0b56be61a21e..bf39f5356ddff9f3b1c1294fcc0364c6707942cb 100644
--- a/doc/src/sgml/ref/drop_function.sgml
+++ b/doc/src/sgml/ref/drop_function.sgml
@@ -1,5 +1,5 @@
@@ -33,7 +33,7 @@ DROP FUNCTION [ IF EXISTS ] name (
function. To execute this command the user must be the
owner of the function. The argument types to the
function must be specified, since several different functions
- may exist with the same name and different argument lists.
+ can exist with the same name and different argument lists.
diff --git a/doc/src/sgml/ref/drop_language.sgml b/doc/src/sgml/ref/drop_language.sgml
index 02e4684454bb5d8be906a57bf72c4a69c0fb192f..ad37287da67ee3d2d3c4252a8337e0f10f2655cf 100644
--- a/doc/src/sgml/ref/drop_language.sgml
+++ b/doc/src/sgml/ref/drop_language.sgml
@@ -1,5 +1,5 @@
@@ -54,7 +54,7 @@ DROP [ PROCEDURAL ] LANGUAGE [ IF EXISTS ] name
The name of an existing procedural language. For backward
- compatibility, the name may be enclosed by single quotes.
+ compatibility, the name can be enclosed by single quotes.
diff --git a/doc/src/sgml/ref/drop_opclass.sgml b/doc/src/sgml/ref/drop_opclass.sgml
index ce00ff40fd52caa950e009fe35140c06af674149..83d770624af5ceb2269edc18248cbabb3687f7a9 100644
--- a/doc/src/sgml/ref/drop_opclass.sgml
+++ b/doc/src/sgml/ref/drop_opclass.sgml
@@ -1,5 +1,5 @@
@@ -102,7 +102,7 @@ DROP OPERATOR CLASS [ IF EXISTS ] nameCREATE OPERATOR CLASS>). An empty operator
- family is harmless, but for the sake of tidiness you may wish to
+ family is harmless, but for the sake of tidiness you might wish to
remove the family with DROP OPERATOR FAMILY>; or perhaps
better, use DROP OPERATOR FAMILY> in the first place.
diff --git a/doc/src/sgml/ref/drop_owned.sgml b/doc/src/sgml/ref/drop_owned.sgml
index fbf101532fff827bd4dade1b1d058116a43da740..6276f8e928e80d31789eb4d31e72f94f64563b45 100644
--- a/doc/src/sgml/ref/drop_owned.sgml
+++ b/doc/src/sgml/ref/drop_owned.sgml
@@ -1,5 +1,5 @@
@@ -81,7 +81,7 @@ DROP OWNED BY name [, ...] [ CASCAD
- Using the CASCADE option may make the command
+ Using the CASCADE option might make the command
recurse to objects owned by other users.
diff --git a/doc/src/sgml/ref/drop_table.sgml b/doc/src/sgml/ref/drop_table.sgml
index 3980f7a294fbbae447518e75bd01c7adfe2f2829..46ee3ac9b09e6128078e99b9ef36bb6b2698a9b4 100644
--- a/doc/src/sgml/ref/drop_table.sgml
+++ b/doc/src/sgml/ref/drop_table.sgml
@@ -1,5 +1,5 @@
@@ -29,7 +29,7 @@ DROP TABLE [ IF EXISTS ] name [, ..
DROP TABLE removes tables from the database.
- Only its owner may destroy a table. To empty a table of rows
+ Only its owner can destroy a table. To empty a table of rows
without destroying the table, use or .
diff --git a/doc/src/sgml/ref/drop_tablespace.sgml b/doc/src/sgml/ref/drop_tablespace.sgml
index 25772eadd3139abb1489008994a04e8ddc1f78e4..bf570d851a0b5922a3e7d1cd3d571159e78c7779 100644
--- a/doc/src/sgml/ref/drop_tablespace.sgml
+++ b/doc/src/sgml/ref/drop_tablespace.sgml
@@ -1,5 +1,5 @@
@@ -34,7 +34,7 @@ DROP TABLESPACE [ IF EXISTS ] tablespacename
A tablespace can only be dropped by its owner or a superuser.
The tablespace must be empty of all database objects before it can be
- dropped. It is possible that objects in other databases may still reside
+ dropped. It is possible that objects in other databases might still reside
in the tablespace even if no objects in the current database are using
the tablespace.
diff --git a/doc/src/sgml/ref/ecpg-ref.sgml b/doc/src/sgml/ref/ecpg-ref.sgml
index 958c97cc1b9ee15262e1e2aafad4eee543931b21..466c52897689864dc99e5d51a96547e3a85411ec 100644
--- a/doc/src/sgml/ref/ecpg-ref.sgml
+++ b/doc/src/sgml/ref/ecpg-ref.sgml
@@ -1,5 +1,5 @@
@@ -80,7 +80,7 @@ PostgreSQL documentation
- Set a compatibility mode. mode may
+ Set a compatibility mode. mode can
be INFORMIX or
INFORMIX_SE.
diff --git a/doc/src/sgml/ref/explain.sgml b/doc/src/sgml/ref/explain.sgml
index b232fb578f7227eef373728a797fc0205416f322..70e2be68ac5da4d5f041db9e2530866ef97c7ae1 100644
--- a/doc/src/sgml/ref/explain.sgml
+++ b/doc/src/sgml/ref/explain.sgml
@@ -1,5 +1,5 @@
@@ -147,7 +147,7 @@ ROLLBACK;
distribution of the data in the table has changed significantly
since the last time ANALYZE was run), the
estimated costs are unlikely to conform to the real properties of
- the query, and consequently an inferior query plan may be chosen.
+ the query, and consequently an inferior query plan might be chosen.
@@ -233,7 +233,7 @@ EXPLAIN ANALYZE EXECUTE query(100, 200);
Of course, the specific numbers shown here depend on the actual
contents of the tables involved. Also note that the numbers, and
- even the selected query strategy, may vary between
+ even the selected query strategy, might vary between
PostgreSQL releases due to planner
improvements. In addition, the ANALYZE command
uses random sampling to estimate data statistics; therefore, it is
diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml
index 4ec1f488f2da62a3812a61ff5730e54568d17cf7..6bb20402fc6360d130557e5359cf3f7942e9e324 100644
--- a/doc/src/sgml/ref/grant.sgml
+++ b/doc/src/sgml/ref/grant.sgml
@@ -1,5 +1,5 @@
@@ -86,8 +86,8 @@ GRANT role [, ...] TO
The key word PUBLIC indicates that the
- privileges are to be granted to all roles, including those that may
- be created later. PUBLIC may be thought of as an
+ privileges are to be granted to all roles, including those that might
+ be created later. PUBLIC can be thought of as an
implicitly defined group that always includes all roles.
Any particular role will have the sum
of privileges granted directly to it, privileges granted to any role it
@@ -97,7 +97,7 @@ GRANT role [, ...] TO
If WITH GRANT OPTION is specified, the recipient
- of the privilege may in turn grant it to others. Without a grant
+ of the privilege can in turn grant it to others. Without a grant
option, the recipient cannot do that. Grant options cannot be granted
to PUBLIC.
@@ -114,17 +114,17 @@ GRANT role [, ...] TO
- Depending on the type of object, the initial default privileges may
+ Depending on the type of object, the initial default privileges might
include granting some privileges to PUBLIC.
The default is no public access for tables, schemas, and tablespaces;
CONNECT> privilege and TEMP> table creation privilege
for databases;
EXECUTE> privilege for functions; and
USAGE> privilege for languages.
- The object owner may of course revoke these privileges. (For maximum
+ The object owner can of course revoke these privileges. (For maximum
security, issue the REVOKE> in the same transaction that
creates the object; then there is no window in which another user
- may use the object.)
+ can use the object.)
@@ -306,7 +306,7 @@ GRANT role [, ...] TO
- If WITH ADMIN OPTION is specified, the member may
+ If WITH ADMIN OPTION is specified, the member can
in turn grant membership in the role to others, and revoke membership
in the role as well. Without the admin option, ordinary users cannot do
that. However,
@@ -448,7 +448,7 @@ GRANT SELECT, UPDATE, INSERT ON mytable TO GROUP todos;
If the Access privileges> column is empty for a given object,
it means the object has default privileges (that is, its privileges column
is null). Default privileges always include all privileges for the owner,
-and may include some privileges for PUBLIC> depending on the
+and can include some privileges for PUBLIC> depending on the
object type, as explained above. The first GRANT> or
REVOKE> on an object
will instantiate the default privileges (producing, for example,
diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml
index 6878a19fa754322ec1e6a552ba757816c4098a1d..6942ad0dfe4cc76e8c5de284a111e87f6c4b19a0 100644
--- a/doc/src/sgml/ref/initdb.sgml
+++ b/doc/src/sgml/ref/initdb.sgml
@@ -1,5 +1,5 @@
@@ -69,7 +69,7 @@ PostgreSQL documentation
initdb must be run as the user that will own the
server process, because the server needs to have access to the
files and directories that initdb creates.
- Since the server may not be run as root, you must not run
+ Since the server cannot be run as root, you must not run
initdb as root either. (It will in fact refuse
to do so.)
@@ -265,7 +265,7 @@ PostgreSQL documentation
By default, when initdb
determines that an error prevented it from completely creating the database
- cluster, it removes any files it may have created before discovering
+ cluster, it removes any files it might have created before discovering
that it can't finish the job. This option inhibits tidying-up and is
thus useful for debugging.
@@ -286,7 +286,7 @@ PostgreSQL documentation
Specifies the directory where the database cluster is to be
- stored; may be overridden using the option.
+ stored; can be overridden using the option.
diff --git a/doc/src/sgml/ref/insert.sgml b/doc/src/sgml/ref/insert.sgml
index a48b335366e12f14e6189ad5706e2bd24fe44963..5dc1f6d7863ccb2c5832592a68efd502ea313c03 100644
--- a/doc/src/sgml/ref/insert.sgml
+++ b/doc/src/sgml/ref/insert.sgml
@@ -1,5 +1,5 @@
@@ -36,7 +36,7 @@ INSERT INTO table [ (
- The target column names may be listed in any order. If no list of
+ The target column names can be listed in any order. If no list of
column names is given at all, the default is all the columns of the
table in their declared order; or the first N> column
names, if there are only N> columns supplied by the
@@ -147,7 +147,7 @@ INSERT INTO table [ (
An expression to be computed and returned by the INSERT>
- command after each row is inserted. The expression may use any
+ command after each row is inserted. The expression can use any
column names of the table.
Write *> to return all columns of the inserted row(s).
diff --git a/doc/src/sgml/ref/ipcclean.sgml b/doc/src/sgml/ref/ipcclean.sgml
index dabc58e48d831d36576a83164a670fe4ac1a8aa5..97f0d8819510365e4a03865c8bd6ffea02094303 100644
--- a/doc/src/sgml/ref/ipcclean.sgml
+++ b/doc/src/sgml/ref/ipcclean.sgml
@@ -1,5 +1,5 @@
@@ -61,8 +61,8 @@ PostgreSQL documentation
The script makes assumptions about the output format of the
ipcs
- utility which may not be true across different operating systems.
- Therefore, it may not work on your particular OS. It's wise to
+ utility which might not be true across different operating systems.
+ Therefore, it might not work on your particular OS. It's wise to
look at the script before trying it.
diff --git a/doc/src/sgml/ref/load.sgml b/doc/src/sgml/ref/load.sgml
index 5fc5817e5f2c7ba7dcf75fe04ebbcea45f174f58..0d9f44bda06a98a6f0b3dba19b9545a5eea14551 100644
--- a/doc/src/sgml/ref/load.sgml
+++ b/doc/src/sgml/ref/load.sgml
@@ -1,5 +1,5 @@
@@ -40,7 +40,7 @@ LOAD 'filename'
The file name is specified in the same way as for shared library
names in ; in particular, one
- may rely on a search path and automatic addition of the system's standard
+ can rely on a search path and automatic addition of the system's standard
shared library file name extension. See for
more information on this topic.
@@ -50,7 +50,7 @@ LOAD 'filename'
- Non-superusers may only apply LOAD> to library files
+ Non-superusers can only apply LOAD> to library files
located in $libdir/plugins/> — the specified
filename must begin
with exactly that string. (It is the database administrator's
diff --git a/doc/src/sgml/ref/notify.sgml b/doc/src/sgml/ref/notify.sgml
index 69d389c8b6636a7334f19623dee7ff97e98227be..9ac1f1db1656651cc859f82276ac246752b015dc 100644
--- a/doc/src/sgml/ref/notify.sgml
+++ b/doc/src/sgml/ref/notify.sgml
@@ -1,5 +1,5 @@
@@ -90,7 +90,7 @@ NOTIFY nameNOTIFY behaves like Unix signals in one important
respect: if the same notification name is signaled multiple times in quick
- succession, recipients may get only one notification event for several executions
+ succession, recipients might get only one notification event for several executions
of NOTIFY. So it is a bad idea to depend on the number
of notifications received. Instead, use NOTIFY to wake up
applications that need to pay attention to something, and use a database
diff --git a/doc/src/sgml/ref/pg_config-ref.sgml b/doc/src/sgml/ref/pg_config-ref.sgml
index 95aa733fceedd46389659cdc59bcd45a2e52f0be..59a2817d2c82a136a98dfe5e6c9b7d5b2378dcb9 100644
--- a/doc/src/sgml/ref/pg_config-ref.sgml
+++ b/doc/src/sgml/ref/pg_config-ref.sgml
@@ -1,4 +1,4 @@
-
+
@@ -106,7 +106,7 @@
Print the location of dynamically loadable modules, or where
the server would search for them. (Other
- architecture-dependent data files may also be installed in this
+ architecture-dependent data files might also be installed in this
directory.)
diff --git a/doc/src/sgml/ref/pg_controldata.sgml b/doc/src/sgml/ref/pg_controldata.sgml
index ab8d1efddf3825a0fc36dd5ec6a0c0a9bfb72eae..658d32f5b091659311bafbaa1c4e9d6bc41fdc52 100644
--- a/doc/src/sgml/ref/pg_controldata.sgml
+++ b/doc/src/sgml/ref/pg_controldata.sgml
@@ -1,5 +1,5 @@
@@ -37,7 +37,7 @@ PostgreSQL documentation
- This utility may only be run by the user who initialized the cluster because
+ This utility can only be run by the user who initialized the cluster because
it requires read access to the data directory.
You can specify the data directory on the command line, or use
the environment variable PGDATA>.
diff --git a/doc/src/sgml/ref/pg_ctl-ref.sgml b/doc/src/sgml/ref/pg_ctl-ref.sgml
index 304ac88e4e8b853392faed2c683bc790856fd0ee..9c2d1e0802a320407347d9365703992f0b388091 100644
--- a/doc/src/sgml/ref/pg_ctl-ref.sgml
+++ b/doc/src/sgml/ref/pg_ctl-ref.sgml
@@ -1,5 +1,5 @@
@@ -203,7 +203,7 @@ PostgreSQL documentation
Specifies the shutdown mode. mode
- may be smart, fast, or
+ can be smart, fast, or
immediate, or the first letter of one of
these three.
@@ -425,7 +425,7 @@ PostgreSQL documentation
Notes
- Waiting for complete start is not a well-defined operation and may
+ Waiting for complete start is not a well-defined operation and might
fail if access control is set up so that a local client cannot
connect without manual interaction (e.g., password authentication). For
additional connection variables, see ,
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 389ac09995c4c18377fdad1871b677220b0e56f4..f71117ad89a3111c2e10c7827bfa148f24b6e42c 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -1,5 +1,5 @@
@@ -120,7 +120,7 @@ PostgreSQL documentation
This option is only meaningful for the plain-text format. For
- the archive formats, you may specify the option when you
+ the archive formats, you can specify the option when you
call pg_restore.
@@ -150,7 +150,7 @@ PostgreSQL documentation
This option is only meaningful for the plain-text format. For
- the archive formats, you may specify the option when you
+ the archive formats, you can specify the option when you
call pg_restore.
@@ -169,7 +169,7 @@ PostgreSQL documentation
This option is only meaningful for the plain-text format. For
- the archive formats, you may specify the option when you
+ the archive formats, you can specify the option when you
call pg_restore.
@@ -188,7 +188,7 @@ PostgreSQL documentation
an error in reloading a row causes only that row to be lost rather
than the entire table contents.
Note that
- the restore may fail altogether if you have rearranged column order.
+ the restore might fail altogether if you have rearranged column order.
The option is safe against column order changes,
though even slower.
@@ -337,7 +337,7 @@ PostgreSQL documentation
When
@@ -410,7 +410,7 @@ PostgreSQL documentation
This option is only meaningful for the plain-text format. For
- the archive formats, you may specify the option when you
+ the archive formats, you can specify the option when you
call pg_restore.
@@ -478,7 +478,7 @@ PostgreSQL documentation
When
@@ -576,7 +576,7 @@ PostgreSQL documentation
This option is only meaningful for the plain-text format. For
- the archive formats, you may specify the option when you
+ the archive formats, you can specify the option when you
call pg_restore.
@@ -589,7 +589,7 @@ PostgreSQL documentation
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
+ depending on the history of the objects in the dump, might not restore
properly. Also, a dump using SET SESSION AUTHORIZATION>
will certainly require superuser privileges to restore correctly,
whereas ALTER OWNER> requires lesser privileges.
@@ -722,7 +722,7 @@ CREATE DATABASE foo WITH TEMPLATE template0;
pg_dump emits commands to disable
triggers on user tables before inserting the data and commands
to re-enable them after the data has been inserted. If the
- restore is stopped in the middle, the system catalogs may be
+ restore is stopped in the middle, the system catalogs might be
left in the wrong state.
diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml
index d0ad93461af64eb5bdfacd95435395d728c256f2..b6d74f1e0d573e22aa42e1aec3abaae32d777cc1 100644
--- a/doc/src/sgml/ref/pg_dumpall.sgml
+++ b/doc/src/sgml/ref/pg_dumpall.sgml
@@ -1,5 +1,5 @@
@@ -106,7 +106,7 @@ PostgreSQL documentation
than COPY). This will make restoration very slow;
it is mainly useful for making dumps that can be loaded into
non-PostgreSQL databases. Note that
- the restore may fail altogether if you have rearranged column order.
+ the restore might fail altogether if you have rearranged column order.
The option is safer, though even slower.
@@ -309,7 +309,7 @@ PostgreSQL documentation
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
+ depending on the history of the objects in the dump, might not restore
properly.
diff --git a/doc/src/sgml/ref/pg_resetxlog.sgml b/doc/src/sgml/ref/pg_resetxlog.sgml
index c1c9754368fca53ef8ffe039bf34804b1116a39a..588ff38c1bb2553ff4175760ba698422dcd8bd51 100644
--- a/doc/src/sgml/ref/pg_resetxlog.sgml
+++ b/doc/src/sgml/ref/pg_resetxlog.sgml
@@ -1,5 +1,5 @@
@@ -42,7 +42,7 @@ PostgreSQL documentation
After running this command, it should be possible to start the server,
- but bear in mind that the database may contain inconsistent data due to
+ but bear in mind that the database might contain inconsistent data due to
partially-committed transactions. You should immediately dump your data,
run initdb>, and reload. After reload, check for
inconsistencies and repair as needed.
@@ -61,7 +61,7 @@ PostgreSQL documentation
valid data for pg_control>, you can force it to proceed anyway
by specifying the -f> (force) switch. In this case plausible
values will be substituted for the missing data. Most of the fields can be
- expected to match, but manual assistance may be needed for the next OID,
+ expected to match, but manual assistance might be needed for the next OID,
next transaction ID and epoch, next multitransaction ID and offset,
WAL starting address, and database locale fields.
The first six of these can be set using the switches discussed below.
@@ -84,14 +84,14 @@ PostgreSQL documentation
epoch, next multitransaction ID, next multitransaction offset, and WAL
starting address values to be set manually. These are only needed when
pg_resetxlog is unable to determine appropriate values
- by reading pg_control>. Safe values may be determined as
+ by reading pg_control>. Safe values can be determined as
follows:
A safe value for the next transaction ID (-x>)
- may be determined by looking for the numerically largest
+ can be determined by looking for the numerically largest
file name in the directory pg_clog> under the data directory,
adding one,
and then multiplying by 1048576. Note that the file names are in
@@ -105,7 +105,7 @@ PostgreSQL documentation
A safe value for the next multitransaction ID (-m>)
- may be determined by looking for the numerically largest
+ can be determined by looking for the numerically largest
file name in the directory pg_multixact/offsets> under the
data directory, adding one, and then multiplying by 65536. As above,
the file names are in hexadecimal, so the easiest way to do this is to
@@ -116,7 +116,7 @@ PostgreSQL documentation
A safe value for the next multitransaction offset (-O>)
- may be determined by looking for the numerically largest
+ can be determined by looking for the numerically largest
file name in the directory pg_multixact/members> under the
data directory, adding one, and then multiplying by 65536. As above,
the file names are in hexadecimal, so the easiest way to do this is to
@@ -179,7 +179,7 @@ PostgreSQL documentation
The -n> (no operation) switch instructs
pg_resetxlog to print the values reconstructed from
pg_control> and then exit without modifying anything.
- This is mainly a debugging tool, but may be useful as a sanity check
+ This is mainly a debugging tool, but can be useful as a sanity check
before allowing pg_resetxlog to proceed for real.
@@ -191,7 +191,7 @@ PostgreSQL documentation
This command must not be used when the server is
running. pg_resetxlog will refuse to start up if
it finds a server lock file in the data directory. If the
- server crashed then a lock file may have been left
+ server crashed then a lock file might have been left
behind; in that case you can remove the lock file to allow
pg_resetxlog to run. But before you do
so, make doubly certain that there is no server process still alive.
diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml
index e7c4ee036e71e497fe78b2176d4554b56b70802b..921069576fd34dc60460ecf8b12e02e391f8fa16 100644
--- a/doc/src/sgml/ref/pg_restore.sgml
+++ b/doc/src/sgml/ref/pg_restore.sgml
@@ -1,4 +1,4 @@
-
+
@@ -233,7 +233,7 @@
Restore elements in
list-file only, and in the
- order they appear in the file. Lines can be moved and may also
+ order they appear in the file. Lines can be moved and can also
be commented out by placing a ; at the
start of the line. (See below for examples.)
@@ -389,7 +389,7 @@
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
+ depending on the history of the objects in the dump, might not restore
properly.
@@ -402,10 +402,10 @@
By default, table data is restored even if the creation command
for the table failed (e.g., because it already exists).
With this option, data for such a table is skipped.
- This behavior is useful when the target database may already
- contain the desired table contents. For example,
+ This behavior is useful if the target database already
+ contains the desired table contents. For example,
auxiliary tables for PostgreSQL> extensions
- such as PostGIS> may already be loaded in
+ such as PostGIS> might already be loaded in
the target database; specifying this option prevents duplicate
or obsolete data from being loaded into them.
@@ -549,7 +549,7 @@ CREATE DATABASE foo WITH TEMPLATE template0;
pg_restore emits commands
to disable triggers on user tables before inserting the data then emits commands to
re-enable them after the data has been inserted. If the restore is stopped in the
- middle, the system catalogs may be left in the wrong state.
+ middle, the system catalogs might be left in the wrong state.
diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml
index 9088c87ec9f5585c2cec50775a4dd1b16e5c2d64..285da158b5d23ad155b725eebc5ae4e69e469a6a 100644
--- a/doc/src/sgml/ref/postgres-ref.sgml
+++ b/doc/src/sgml/ref/postgres-ref.sgml
@@ -1,5 +1,5 @@
@@ -354,13 +354,13 @@ PostgreSQL documentation
Semi-internal Options
- There are several other options that may be specified, used
+ There are several other options that can be specified, used
mainly for debugging purposes and in some cases to assist with
recovery of severely damaged databases. There should be no reason
to use them in a production database setup. These are listed
here only for the use by PostgreSQL
- system developers. Furthermore, any of these options may
- disappear or change in a future release without notice.
+ system developers. Furthermore, these options might
+ change or be removed in a future release without notice.
@@ -559,7 +559,7 @@ PostgreSQL documentation
- Default character encoding used by clients. (The clients may
+ Default character encoding used by clients. (The clients can
override this individually.) This value can also be set in the
configuration file.
@@ -617,7 +617,7 @@ PostgreSQL documentation
A failure message mentioning semget> or
shmget> probably indicates you need to configure your
kernel to provide adequate shared memory and semaphores. For more
- discussion see . You may be able
+ discussion see . You might be able
to postpone reconfiguring your kernel by decreasing to reduce the shared memory
consumption of PostgreSQL>, and/or by reducing
@@ -636,18 +636,18 @@ PostgreSQL documentation
$ps -ef | grep postgres
depending on your system. If you are certain that no conflicting
- server is running, you may remove the lock file mentioned in the
+ server is running, you can remove the lock file mentioned in the
message and try again.
- A failure message indicating inability to bind to a port may
+ A failure message indicating inability to bind to a port might
indicate that that port is already in use by some
- non-PostgreSQL process. You may also
+ non-PostgreSQL process. You might also
get this error if you terminate postgres
and immediately restart it using the same port; in this case, you
must simply wait a few seconds until the operating system closes
- the port before trying again. Finally, you may get this error if
+ the port before trying again. Finally, you might get this error if
you specify a port number that your operating system considers to
be reserved. For example, many versions of Unix consider port
numbers under 1024 to be trusted and only permit
@@ -665,7 +665,7 @@ PostgreSQL documentation
postgres server. Doing so will prevent
postgres from freeing the system
resources (e.g., shared memory and semaphores) that it holds before
- terminating. This may cause problems for starting a fresh
+ terminating. This might cause problems for starting a fresh
postgres run.
diff --git a/doc/src/sgml/ref/prepare.sgml b/doc/src/sgml/ref/prepare.sgml
index b4d9ab64dc22d05b5afd6cc2f9ffba461af7ea82..62097152beb91dee6fe44eebb1da8323e362e113 100644
--- a/doc/src/sgml/ref/prepare.sgml
+++ b/doc/src/sgml/ref/prepare.sgml
@@ -1,5 +1,5 @@
@@ -138,7 +138,7 @@ PREPARE name [ (PostgreSQL has chosen for a prepared
statement, use .
diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml
index 3a6af2b537f8412d9327e59e6f5f92135129df0a..5f1057c2ce2dd8807098a3d8b39d66c344e8cebf 100644
--- a/doc/src/sgml/ref/psql-ref.sgml
+++ b/doc/src/sgml/ref/psql-ref.sgml
@@ -1,5 +1,5 @@
@@ -601,7 +601,7 @@ testdb=>
- At the prompt, the user may type in SQL commands.
+ At the prompt, the user can type in SQL commands.
Ordinarily, input lines are sent to the server when a
command-terminating semicolon is reached. An end of line does not
terminate a command. Thus commands can be spread over several lines for
@@ -638,7 +638,7 @@ testdb=>
- To include whitespace into an argument you may quote it with a
+ To include whitespace into an argument you can quote it with a
single quote. To include a single quote into such an argument,
use two single quotes. Anything contained in single quotes is
furthermore subject to C-like substitutions for
@@ -819,7 +819,7 @@ testdb=>
This operation is not as efficient as the SQL
COPY command because all data must pass
through the client/server connection. For large
- amounts of data the SQL command may be preferable.
+ amounts of data the SQL command might be preferable.
@@ -1172,7 +1172,7 @@ Tue Oct 26 21:40:57 CEST 1999
If you use the \o command to redirect your
- query output you may wish to use \qecho
+ query output you might wish to use \qecho
instead of this command.
@@ -1566,8 +1566,8 @@ lo_import 152801
tuples_only (or t)
- Toggles between tuples only and full display. Full display may
- show extra information such as column headers, titles, and
+ Toggles between tuples only and full display. Full display
+ shows extra information such as column headers, titles, and
various footers. In tuples only mode, only actual table data
is shown.
@@ -2022,7 +2022,7 @@ bar
The autocommit-on mode is PostgreSQL>'s traditional
behavior, but autocommit-off is closer to the SQL spec. If you
- prefer autocommit-off, you may wish to set it in the system-wide
+ prefer autocommit-off, you might wish to set it in the system-wide
psqlrc file or your
~/.psqlrc file.
@@ -2093,7 +2093,7 @@ bar
limited amount of memory is used, regardless of the size of
the result set. Settings of 100 to 1000 are commonly used
when enabling this feature.
- Keep in mind that when using this feature, a query may
+ Keep in mind that when using this feature, a query might
fail after having already displayed some rows.
@@ -2387,7 +2387,7 @@ testdb=> \set content '''' `sed -e "s/'/''/g" -e 's/\\/\\\\/g' <
- Since colons may legally appear in SQL commands, the following rule
+ Since colons can legally appear in SQL commands, the following rule
applies: the character sequence
:name is not changed unless name> is the name
of a variable that is currently set. In any case you can escape
@@ -2559,13 +2559,13 @@ testdb=> \set content '''' `sed -e "s/'/''/g" -e 's/\\/\\\\/g' <
%[ ... %]
- Prompts may contain terminal control characters which, for
+ Prompts can contain terminal control characters which, for
example, change the color, background, or style of the prompt
text, or change the title of the terminal window. In order for
the line editing features of Readline to work properly, these
non-printing control characters must be designated as invisible
by surrounding them with %[ and
- %]. Multiple pairs of these may occur within
+ %]. Multiple pairs of these can occur within
the prompt. For example,
testdb=> \set PROMPT1 '%[%033[1;33;40m%]%n@%/%R%[%033[0m%]%# '
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index f8e4ef7d5e9569e8c87048b78d0f675ba10281a0..d6d1a13279e39d59b1a9b8c23cac18069dd96f42 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -1,5 +1,5 @@
@@ -37,7 +37,7 @@ REINDEX { INDEX | TABLE | DATABASE | SYSTEM } nam
An index has become corrupted, and no longer contains valid
data. Although in theory this should never happen, in
- practice indexes may become corrupted due to software bugs or
+ practice indexes can become corrupted due to software bugs or
hardware failures. REINDEX provides a
recovery method.
@@ -130,7 +130,7 @@ REINDEX { INDEX | TABLE | DATABASE | SYSTEM } nam
The name of the specific index, table, or database to be
- reindexed. Index and table names may be schema-qualified.
+ reindexed. Index and table names can be schema-qualified.
Presently, REINDEX DATABASE> and REINDEX SYSTEM>
can only reindex the current database, so their parameter must match
the current database's name.
@@ -162,7 +162,7 @@ REINDEX { INDEX | TABLE | DATABASE | SYSTEM } nam
Things are more difficult if you need to recover from corruption of
an index on a system table. In this case it's important for the
system to not have used any of the suspect indexes itself.
- (Indeed, in this sort of scenario you may find that server
+ (Indeed, in this sort of scenario you might find that server
processes are crashing immediately at start-up, due to reliance on
the corrupted indexes.) To recover safely, the server must be started
with the option, which prevents it from using
@@ -191,7 +191,7 @@ REINDEX { INDEX | TABLE | DATABASE | SYSTEM } nam
libpq>-based clients, it is possible to set
the PGOPTIONS environment variable to -P>
before starting the client. Note that while this method does not
- require locking out other clients, it may still be wise to prevent
+ require locking out other clients, it might still be wise to prevent
other users from connecting to the damaged database until repairs
have been completed.
@@ -230,7 +230,7 @@ REINDEX { INDEX | TABLE | DATABASE | SYSTEM } nam
exclusive lock on the parent table, blocking both writes and reads. The
subsequent CREATE INDEX> locks out writes but not reads; since
the index is not there, no read will attempt to use it, meaning that there
- will be no blocking but reads may be forced into expensive sequential
+ will be no blocking but reads might be forced into expensive sequential
scans. Another important point is that the drop/create approach
invalidates any cached query plans that use the index, while
REINDEX> does not.
diff --git a/doc/src/sgml/ref/release_savepoint.sgml b/doc/src/sgml/ref/release_savepoint.sgml
index 4ce8af4b087d1497004e3019b8243218f81e3ae2..1ba4fc7ed6b656178715d331fa242beb37336a88 100644
--- a/doc/src/sgml/ref/release_savepoint.sgml
+++ b/doc/src/sgml/ref/release_savepoint.sgml
@@ -1,5 +1,5 @@
@@ -43,7 +43,7 @@ RELEASE [ SAVEPOINT ] savepoint_name
effects of commands executed after the savepoint was established.
(To do that, see .) Destroying a savepoint when
- it is no longer needed may allow the system to reclaim some resources
+ it is no longer needed allows the system to reclaim some resources
earlier than transaction end.
diff --git a/doc/src/sgml/ref/revoke.sgml b/doc/src/sgml/ref/revoke.sgml
index e093cc4b80bc909fe55aaaf446647e8b4d1c5ce4..caf62b78331fe994dd7d02cf6e473806d3cec836 100644
--- a/doc/src/sgml/ref/revoke.sgml
+++ b/doc/src/sgml/ref/revoke.sgml
@@ -1,5 +1,5 @@
@@ -111,7 +111,7 @@ REVOKE [ ADMIN OPTION FOR ]
will fail. This recursive revocation only affects privileges that
were granted through a chain of users that is traceable to the user
that is the subject of this REVOKE command.
- Thus, the affected users may effectively keep the privilege if it
+ Thus, the affected users might effectively keep the privilege if it
was also granted through other users.
@@ -163,7 +163,7 @@ REVOKE [ ADMIN OPTION FOR ]
command, the command is performed as though it were issued by the
owner of the affected object. Since all privileges ultimately come
from the object owner (possibly indirectly via chains of grant options),
- it is possible for a superuser to revoke all privileges, but this may
+ it is possible for a superuser to revoke all privileges, but this might
require use of CASCADE as stated above.
@@ -187,7 +187,7 @@ REVOKE [ ADMIN OPTION FOR ]
indirectly via more than one role membership path, it is unspecified
which containing role will be used to perform the command. In such cases
it is best practice to use SET ROLE> to become the specific
- role you want to do the REVOKE> as. Failure to do so may
+ role you want to do the REVOKE> as. Failure to do so might
lead to revoking privileges other than the ones you intended, or not
revoking anything at all.
diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml
index f77b805118d139b3a54d3b61886ea28a0df919f3..ca101571d01b9b853fbcd89a03ca6753644eb128 100644
--- a/doc/src/sgml/ref/select.sgml
+++ b/doc/src/sgml/ref/select.sgml
@@ -1,5 +1,5 @@
@@ -242,7 +242,7 @@ where from_item can be one of:
result sets, but any function can be used.) This acts as
though its output were created as a temporary table for the
duration of this single SELECT command. An
- alias may also be used. If an alias is written, a column alias
+ alias can also be used. If an alias is written, a column alias
list can also be written to provide substitute names for one
or more attributes of the function's composite return type. If
the function has been defined as returning the record>
@@ -287,7 +287,7 @@ where from_item can be one of:
USING (join_column [, ...]).
See below for the meaning. For CROSS JOIN,
- none of these clauses may appear.
+ none of these clauses can appear.
@@ -542,7 +542,7 @@ HAVING condition
- Currently, FOR UPDATE> and FOR SHARE> may not be
+ Currently, FOR UPDATE> and FOR SHARE> cannot be
specified either for a UNION> result or for any input of a
UNION>.
@@ -588,7 +588,7 @@ HAVING condition
- Currently, FOR UPDATE> and FOR SHARE> may not be
+ Currently, FOR UPDATE> and FOR SHARE> cannot be
specified either for an INTERSECT> result or for any input of
an INTERSECT>.
@@ -630,7 +630,7 @@ HAVING condition
- Currently, FOR UPDATE> and FOR SHARE> may not be
+ Currently, FOR UPDATE> and FOR SHARE> cannot be
specified either for an EXCEPT> result or for any input of
an EXCEPT>.
@@ -678,7 +678,7 @@ SELECT name FROM distributors ORDER BY code;
A limitation of this feature is that an ORDER BY>
clause applying to the result of a UNION>,
- INTERSECT>, or EXCEPT> clause may only
+ INTERSECT>, or EXCEPT> clause can only
specify an output column name or number, not an expression.
@@ -692,11 +692,11 @@ SELECT name FROM distributors ORDER BY code;
- Optionally one may add the key word ASC> (ascending) or
+ Optionally one can add the key word ASC> (ascending) or
DESC> (descending) after any expression in the
ORDER BY> clause. If not specified, ASC> is
assumed by default. Alternatively, a specific ordering operator
- name may be specified in the USING> clause.
+ name can be specified in the USING> clause.
An ordering operator must be a less-than or greater-than
member of some btree operator family.
ASC> is usually equivalent to USING <> and
@@ -792,7 +792,7 @@ OFFSET start
When using LIMIT>, it is a good idea to use an
ORDER BY> clause that constrains the result rows into a
unique order. Otherwise you will get an unpredictable subset of
- the query's rows — you may be asking for the tenth through
+ the query's rows — you might be asking for the tenth through
twentieth rows, but tenth through twentieth in what ordering? You
don't know what ordering unless you specify ORDER BY>.
@@ -1144,9 +1144,9 @@ SELECT distributors.* WHERE distributors.name = 'Westward';
Namespace Available to GROUP BY and ORDER BY
- In the SQL-92 standard, an ORDER BY clause may
+ In the SQL-92 standard, an ORDER BY clause can
only use result column names or numbers, while a GROUP
- BY clause may only use expressions based on input column
+ BY clause can only use expressions based on input column
names. PostgreSQL extends each of
these clauses to allow the other choice as well (but it uses the
standard's interpretation if there is ambiguity).
diff --git a/doc/src/sgml/ref/set_role.sgml b/doc/src/sgml/ref/set_role.sgml
index 96be6e9fbf76d136f606de78f895e1d707f086a9..d58943fbefe17de2b4e35bcc152c4a8825b2c0c7 100644
--- a/doc/src/sgml/ref/set_role.sgml
+++ b/doc/src/sgml/ref/set_role.sgml
@@ -1,5 +1,5 @@
@@ -32,7 +32,7 @@ RESET ROLE
This command sets the current user
identifier of the current SQL-session context to be rolename. The role name may be
+ class="parameter">rolename. The role name can be
written as either an identifier or a string literal.
After SET ROLE>, permissions checking for SQL commands
is carried out as though the named role were the one that had logged
@@ -54,7 +54,7 @@ RESET ROLE
The NONE> and RESET> forms reset the current
user identifier to be the current session user identifier.
- These forms may be executed by any user.
+ These forms can be executed by any user.
diff --git a/doc/src/sgml/ref/set_session_auth.sgml b/doc/src/sgml/ref/set_session_auth.sgml
index dc64a6c24ff5b8cdb3df0b7293b49de9c4c224ad..315aec14e7c88d7d157efeedd9bdb9a515f0d24d 100644
--- a/doc/src/sgml/ref/set_session_auth.sgml
+++ b/doc/src/sgml/ref/set_session_auth.sgml
@@ -1,4 +1,4 @@
-
+
SET SESSION AUTHORIZATION
@@ -28,7 +28,7 @@ RESET SESSION AUTHORIZATION
This command sets the session user identifier and the current user
identifier of the current SQL-session context to be username. The user name may be
+ class="parameter">username. The user name can be
written as either an identifier or a string literal. Using this
command, it is possible, for example, to temporarily become an
unprivileged user and later switch back to being a superuser.
@@ -38,14 +38,14 @@ RESET SESSION AUTHORIZATION
The session user identifier is initially set to be the (possibly
authenticated) user name provided by the client. The current user
identifier is normally equal to the session user identifier, but
- may change temporarily in the context of setuid
+ might change temporarily in the context of setuid
functions and similar mechanisms; it can also be changed by
.
The current user identifier is relevant for permission checking.
- The session user identifier may be changed only if the initial session
+ The session user identifier can be changed only if the initial session
user (the authenticated user) had the
superuser privilege. Otherwise, the command is accepted only if it
specifies the authenticated user name.
@@ -60,7 +60,7 @@ RESET SESSION AUTHORIZATION
The DEFAULT> and RESET> forms reset the session
and current user identifiers to be the originally authenticated user
- name. These forms may be executed by any user.
+ name. These forms can be executed by any user.
diff --git a/doc/src/sgml/ref/start_transaction.sgml b/doc/src/sgml/ref/start_transaction.sgml
index 300ed0c33a22e0fd4d25cc7241c2278e2375fb57..d678b5e4fb9e0efab57669c90aa64b19168e9138 100644
--- a/doc/src/sgml/ref/start_transaction.sgml
+++ b/doc/src/sgml/ref/start_transaction.sgml
@@ -1,5 +1,5 @@
@@ -61,7 +61,7 @@ where transaction_mode is one of:
issuing a COMMIT after each command that does not
follow START TRANSACTION> (or BEGIN),
and it is therefore often called autocommit>.
- Other relational database systems may offer an autocommit feature
+ Other relational database systems might offer an autocommit feature
as a convenience.
diff --git a/doc/src/sgml/ref/truncate.sgml b/doc/src/sgml/ref/truncate.sgml
index fb55a4014d1044f0a9f0573c2ea9dd88bb2d9c00..79ed75b4999713919772d692e01755cb04a02692 100644
--- a/doc/src/sgml/ref/truncate.sgml
+++ b/doc/src/sgml/ref/truncate.sgml
@@ -1,5 +1,5 @@
@@ -75,7 +75,7 @@ TRUNCATE [ TABLE ] name [, ...] [ C
Notes
- Only the owner of a table may TRUNCATE> it.
+ Only the owner of a table can TRUNCATE> it.
diff --git a/doc/src/sgml/ref/unlisten.sgml b/doc/src/sgml/ref/unlisten.sgml
index 620a0dd5b6fca9ebd3232eea61975f62ab16ff2a..79d4681cdf14a1936d4e9928157327d6b364800e 100644
--- a/doc/src/sgml/ref/unlisten.sgml
+++ b/doc/src/sgml/ref/unlisten.sgml
@@ -1,5 +1,5 @@
@@ -74,7 +74,7 @@ UNLISTEN { name | * }
Notes
- You may unlisten something you were not listening for; no warning or error
+ You can unlisten something you were not listening for; no warning or error
will appear.
diff --git a/doc/src/sgml/ref/update.sgml b/doc/src/sgml/ref/update.sgml
index 64120292e597538fe8042ba03c9cc13ce745bd87..5624a3cb097cb00a8a614c4578c85f0348e9c8a7 100644
--- a/doc/src/sgml/ref/update.sgml
+++ b/doc/src/sgml/ref/update.sgml
@@ -1,5 +1,5 @@
@@ -117,7 +117,7 @@ UPDATE [ ONLY ] table [ [ AS ] expression
- An expression to assign to the column. The expression may use the
+ An expression to assign to the column. The expression can use the
old values of this and other columns in the table.
@@ -165,7 +165,7 @@ UPDATE [ ONLY ] table [ [ AS ]
An expression to be computed and returned by the UPDATE>
- command after each row is updated. The expression may use any
+ command after each row is updated. The expression can use any
column names of the table
or table(s) listed in FROM>.
Write *> to return all columns.
diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index a9e86a24c800dd3c1f8725788421bd095ced4a69..a2c45b5a0c7933105d36d26620115dd07b051fd6 100644
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -1,5 +1,5 @@
@@ -72,7 +72,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ FULL
- Selects full vacuum, which may reclaim more
+ Selects full vacuum, which can reclaim more
space, but takes much longer and exclusively locks the table.
@@ -153,7 +153,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [
We recommend that active production databases be
vacuumed frequently (at least nightly), in order to
remove dead rows. After adding or deleting a large number
- of rows, it may be a good idea to issue a VACUUM
+ of rows, it might be a good idea to issue a VACUUM
ANALYZE command for the affected table. This will update the
system catalogs with
the results of all recent changes, and allow the
@@ -163,7 +163,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [
The option is not recommended for routine use,
- but may be useful in special cases. An example is when you have deleted
+ but might be useful in special cases. An example is when you have deleted
most of the rows in a table and would like the table to physically shrink
to occupy less disk space. VACUUM FULL will usually
shrink the table more than a plain VACUUM would.
@@ -174,7 +174,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ VACUUM causes a substantial increase in I/O traffic,
- which can cause poor performance for other active sessions. Therefore,
+ which might cause poor performance for other active sessions. Therefore,
it is sometimes advisable to use the cost-based vacuum delay feature.
See for details.
diff --git a/doc/src/sgml/ref/vacuumdb.sgml b/doc/src/sgml/ref/vacuumdb.sgml
index bbeb34ff6de6777845f2f0a008fc8ddabc9697d5..6159e9bca80eec5b22ce7134bcc54a8fae33c39b 100644
--- a/doc/src/sgml/ref/vacuumdb.sgml
+++ b/doc/src/sgml/ref/vacuumdb.sgml
@@ -1,5 +1,5 @@
@@ -130,7 +130,7 @@ PostgreSQL documentation
Clean or analyze table only.
- Column names may be specified only in conjunction with
+ Column names can be specified only in conjunction with
the option.
diff --git a/doc/src/sgml/ref/values.sgml b/doc/src/sgml/ref/values.sgml
index eedf431ebff0b8546428b42d9e2228346c8b2144..3a28e5dd438bb2527617ed92044e16c52785eae3 100644
--- a/doc/src/sgml/ref/values.sgml
+++ b/doc/src/sgml/ref/values.sgml
@@ -1,5 +1,5 @@
@@ -78,7 +78,7 @@ VALUES ( expression [, ...] ) [, ..
An expression or integer constant indicating how to sort the result
- rows. This expression may refer to the columns of the
+ rows. This expression can refer to the columns of the
VALUES> result as column1>, column2>,
etc. For more details see
.
@@ -124,7 +124,7 @@ VALUES ( expression [, ...] ) [, ..
VALUES> lists with very large numbers of rows should be avoided,
- as you may encounter out-of-memory failures or poor performance.
+ as you might encounter out-of-memory failures or poor performance.
VALUES> appearing within INSERT> is a special case
(because the desired column types are known from the INSERT>'s
target table, and need not be inferred by scanning the VALUES>
@@ -203,7 +203,7 @@ UPDATE employees SET salary = salary * v.increase
When VALUES> is used in INSERT>, the values are all
automatically coerced to the data type of the corresponding destination
- column. When it's used in other contexts, it may be necessary to specify
+ column. When it's used in other contexts, it might be necessary to specify
the correct data type. If the entries are all quoted literal constants,
coercing the first is sufficient to determine the assumed type for all: