mirror of
https://github.com/postgres/postgres.git
synced 2025-07-18 17:42:25 +03:00
doc: Various typo/grammar fixes
Errors detected using Topy (https://github.com/intgr/topy), all changes verified by hand and some manual tweaks added. Marti Raudsepp Individual changes backpatched, where applicable, as far as 9.0.
This commit is contained in:
@ -2239,7 +2239,7 @@ January 8 04:05:06 1999 PST
|
||||
<para>
|
||||
Time zones, and time-zone conventions, are influenced by
|
||||
political decisions, not just earth geometry. Time zones around the
|
||||
world became somewhat standardized during the 1900's,
|
||||
world became somewhat standardized during the 1900s,
|
||||
but continue to be prone to arbitrary changes, particularly with
|
||||
respect to daylight-savings rules.
|
||||
<productname>PostgreSQL</productname> uses the widely-used
|
||||
|
@ -637,7 +637,7 @@ END;
|
||||
(useful when multiple scripts were specified with <literal>-f</>),
|
||||
and <replaceable>time_epoch</>/<replaceable>time_us</> are a
|
||||
UNIX epoch format timestamp and an offset
|
||||
in microseconds (suitable for creating a ISO 8601
|
||||
in microseconds (suitable for creating an ISO 8601
|
||||
timestamp with fractional seconds) showing when
|
||||
the transaction completed.
|
||||
</para>
|
||||
|
@ -538,7 +538,7 @@ pgp_pub_encrypt_bytea(data bytea, key bytea [, options text ]) returns bytea
|
||||
</synopsis>
|
||||
<para>
|
||||
Encrypt <parameter>data</> with a public PGP key <parameter>key</>.
|
||||
Giving this function a secret key will produce a error.
|
||||
Giving this function a secret key will produce an error.
|
||||
</para>
|
||||
<para>
|
||||
The <parameter>options</> parameter can contain option settings,
|
||||
|
@ -51,7 +51,7 @@
|
||||
Sometimes it is desirable to write Tcl functions that are not restricted
|
||||
to safe Tcl. For example, one might want a Tcl function that sends
|
||||
email. To handle these cases, there is a variant of <application>PL/Tcl</> called <literal>PL/TclU</>
|
||||
(for untrusted Tcl). This is the exact same language except that a full
|
||||
(for untrusted Tcl). This is exactly the same language except that a full
|
||||
Tcl interpreter is used. <emphasis>If <application>PL/TclU</> is used, it must be
|
||||
installed as an untrusted procedural language</emphasis> so that only
|
||||
database superusers can create functions in it. The writer of a <application>PL/TclU</>
|
||||
|
@ -116,7 +116,7 @@ ALTER TEXT SEARCH DICTIONARY my_dict ( StopWords = newrussian );
|
||||
</programlisting>
|
||||
|
||||
<para>
|
||||
The following example command changes the language option to dutch,
|
||||
The following example command changes the language option to <literal>dutch</>,
|
||||
and removes the stopword option entirely.
|
||||
</para>
|
||||
|
||||
|
@ -265,7 +265,7 @@ COMMENT ON SEQUENCE my_sequence IS 'Used to generate primary keys';
|
||||
COMMENT ON TABLE my_schema.my_table IS 'Employee Information';
|
||||
COMMENT ON TABLESPACE my_tablespace IS 'Tablespace for indexes';
|
||||
COMMENT ON TEXT SEARCH CONFIGURATION my_config IS 'Special word filtering';
|
||||
COMMENT ON TEXT SEARCH DICTIONARY swedish IS 'Snowball stemmer for swedish language';
|
||||
COMMENT ON TEXT SEARCH DICTIONARY swedish IS 'Snowball stemmer for Swedish language';
|
||||
COMMENT ON TEXT SEARCH PARSER my_parser IS 'Splits text into words';
|
||||
COMMENT ON TEXT SEARCH TEMPLATE snowball IS 'Snowball stemmer';
|
||||
COMMENT ON TRIGGER my_trigger ON my_table IS 'Used for RI';
|
||||
|
@ -3797,7 +3797,7 @@ DROP SCHEMA information_schema CASCADE;
|
||||
</para>
|
||||
<para>
|
||||
This enabled <command>GRANT</command> to give other users the
|
||||
ability to grant privileges on a object.
|
||||
ability to grant privileges on an object.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
@ -5883,7 +5883,7 @@
|
||||
<para>
|
||||
The new syntax is <link linkend="SQL-CREATEINDEX"><command>CREATE
|
||||
INDEX CONCURRENTLY</></link>. The default behavior is
|
||||
still to block table modification while a index is being
|
||||
still to block table modification while an index is being
|
||||
created.
|
||||
</para>
|
||||
</listitem>
|
||||
|
@ -4849,7 +4849,7 @@ New DECLARE and FETCH feature(Thomas)
|
||||
libpq's internal structures now not exported(Tom)
|
||||
Allow up to 8 key indexes(Bruce)
|
||||
Remove ARCHIVE key word, that is no longer used(Thomas)
|
||||
pg_dump -n flag to suppress quotes around indentifiers
|
||||
pg_dump -n flag to suppress quotes around identifiers
|
||||
disable system columns for views(Jan)
|
||||
new INET and CIDR types for network addresses(TomH, Paul)
|
||||
no more double quotes in psql output
|
||||
@ -5250,7 +5250,7 @@ Support SQL92 syntax for type coercion of literal strings
|
||||
(e.g. "DATETIME 'now'")(Thomas)
|
||||
Add conversions for int2, int4, and OID types to and from text(Thomas)
|
||||
Use shared lock when building indexes(Vadim)
|
||||
Free memory allocated for an user query inside transaction block after
|
||||
Free memory allocated for a user query inside transaction block after
|
||||
this query is done, was turned off in <= 6.2.1(Vadim)
|
||||
New SQL statement CREATE PROCEDURAL LANGUAGE(Jan)
|
||||
New <productname>PostgreSQL</productname> Procedural Language (PL) backend interface(Jan)
|
||||
@ -6514,7 +6514,7 @@ Incompatible changes:
|
||||
New tools:
|
||||
* pgperl - a Perl (4.036) interface to Postgres95
|
||||
* pg_dump - a utility for dumping out a postgres database into a
|
||||
script file containing query commands. The script files are in a ASCII
|
||||
script file containing query commands. The script files are in an ASCII
|
||||
format and can be used to reconstruct the database, even on other
|
||||
machines and other architectures. (Also good for converting
|
||||
a Postgres 4.2 database to Postgres95 database.)
|
||||
|
@ -546,7 +546,7 @@
|
||||
|
||||
;; By default, the part and reference title pages get wrong page
|
||||
;; numbers: The first title page gets roman numerals carried over from
|
||||
;; preface/toc -- we want arabic numerals. We also need to make sure
|
||||
;; preface/toc -- we want Arabic numerals. We also need to make sure
|
||||
;; that page-number-restart is set of #f explicitly, because otherwise
|
||||
;; it will carry over from the previous component, which is not good.
|
||||
;;
|
||||
|
@ -2425,7 +2425,7 @@ more sample word(s) : more indexed word(s)
|
||||
</programlisting>
|
||||
|
||||
where the colon (<symbol>:</symbol>) symbol acts as a delimiter between a
|
||||
a phrase and its replacement.
|
||||
phrase and its replacement.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
@ -321,7 +321,7 @@ AS t(article_id integer, author text, page_count integer, title text);
|
||||
|
||||
<para>
|
||||
The calling <command>SELECT</> statement doesn't necessarily have be
|
||||
be just <literal>SELECT *</> — it can reference the output
|
||||
just <literal>SELECT *</> — it can reference the output
|
||||
columns by name or join them to other tables. The function produces a
|
||||
virtual table with which you can perform any operation you wish (e.g.
|
||||
aggregation, joining, sorting etc). So we could also have:
|
||||
|
@ -189,7 +189,7 @@ SELECT (a + b) AS c FROM test_complex;
|
||||
|
||||
<para>
|
||||
Unlike commutators, a pair of unary operators could validly be marked
|
||||
as each others' negators; that would mean (A x) equals NOT (B x)
|
||||
as each other's negators; that would mean (A x) equals NOT (B x)
|
||||
for all x, or the equivalent for right unary operators.
|
||||
</para>
|
||||
|
||||
|
Reference in New Issue
Block a user