diff options
author | Bruce Momjian <bruce@momjian.us> | 2007-01-31 23:26:05 +0000 |
---|---|---|
committer | Bruce Momjian <bruce@momjian.us> | 2007-01-31 23:26:05 +0000 |
commit | e81c138e18b54e272d917e5e8c4c8ae1b89cd133 (patch) | |
tree | 578b3af0265e9767b862475ee4ba7e9a40c22dc2 /doc/src/sgml/ref/create_sequence.sgml | |
parent | bc799fab2ba314425403073565775ffe15ba4406 (diff) |
Update reference documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
Diffstat (limited to 'doc/src/sgml/ref/create_sequence.sgml')
-rw-r--r-- | doc/src/sgml/ref/create_sequence.sgml | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/src/sgml/ref/create_sequence.sgml b/doc/src/sgml/ref/create_sequence.sgml index f24610d1e43..bd3c4ac8699 100644 --- a/doc/src/sgml/ref/create_sequence.sgml +++ b/doc/src/sgml/ref/create_sequence.sgml @@ -1,5 +1,5 @@ <!-- -$PostgreSQL: pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.45 2006/09/16 00:30:17 momjian Exp $ +$PostgreSQL: pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.46 2007/01/31 23:26:03 momjian Exp $ PostgreSQL documentation --> @@ -41,7 +41,7 @@ CREATE [ TEMPORARY | TEMP ] SEQUENCE <replaceable class="parameter">name</replac <para> 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 <replaceable>name</replaceable>; to examine the parameters and current state of a sequence. In particular, the <literal>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 <function>nextval</> calls.) </para> @@ -224,13 +224,13 @@ SELECT * FROM <replaceable>name</replaceable>; Sequences are based on <type>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 <type>integer</> arithmetic (range -2147483648 to +2147483647). </para> <para> - Unexpected results may be obtained if a <replaceable + Unexpected results might be obtained if a <replaceable class="parameter">cache</replaceable> 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 <replaceable>name</replaceable>; <para> 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 <replaceable class="parameter">cache</replaceable> setting of 10, session A might reserve values 1..10 and return |