From: Alexander Law <exclusion@gmail.com>
To: pgsql-docs@postgresql.org <pgsql-docs@postgresql.org>
Subject: Fix some typos
Date: Sat, 13 May 2017 18:59:21 +0300
Message-ID: <374e84e6-f89b-4d0a-652c-cb2449f0bfc4@gmail.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
Hello,
Please consider committing the attached patches for docs. (One of them
is affecting a comment in src/.)
Also I found some inconsistent spellings of the names, but I'm not sure
whether it should be fixed:
1. "Hans-Jurgen Schonig" and "Hans-Juergen Schoenig".
Maybe it's better to spell it as "/Hans-//Jürgen Schönig/"?
2. "Kondo Mitsumasa" and "Mitsumasa Kondo"
The former one is encountered only once so maybe it should be replaced
with the latter.
3. "Alex Shulgin", "Alexander Shulgin", and "Oleksandr Shulgin"
I believe that the correct name spelling is "Alexander".
--
Alexander Lakhin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docsAttachments:download all (7 files, .tar.gz)concatentate.patch (text/x-patch, 744B) downloaddiff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgmlindex d556567..620bf9b 100644--- a/doc/src/sgml/func.sgml+++ b/doc/src/sgml/func.sgml@@ -9571,7 +9571,7 @@ CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple
<entry><type>tsvector</type></entry>
<entry>
reduce each string value in the document to a <type>tsvector</>, and then
- concatentate those in document order to produce a single <type>tsvector</>+ concatenate those in document order to produce a single <type>tsvector</>
</entry>
<entry><literal>to_tsvector('english', '{"a": "The Fat Rats"}'::json)</literal></entry>
<entry><literal>'fat':2 'rat':3</literal></entry>
existance.patch (text/x-patch, 569B) downloaddiff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgmlindex 32e17ee..67031c8 100644--- a/doc/src/sgml/perform.sgml+++ b/doc/src/sgml/perform.sgml@@ -1111,7 +1111,7 @@ WHERE tablename = 'road';
</para>
<para>
- The existance of functional dependencies directly affects the accuracy+ The existence of functional dependencies directly affects the accuracy
of estimates in certain queries.
The reason is that conditions on the dependent columns do not
restrict the result set, but the query planner (lacking functional
failback.patch (text/x-patch, 563B) downloaddiff --git a/doc/src/sgml/release-9.5.sgml b/doc/src/sgml/release-9.5.sgmlindex 14a9b9d..7fd4dee 100644--- a/doc/src/sgml/release-9.5.sgml+++ b/doc/src/sgml/release-9.5.sgml@@ -6918,7 +6918,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
<para>
Add <link linkend="app-pgrewind"><application>pg_rewind</></>,
- which allows re-synchronizing a master server after failback+ which allows re-synchronizing a master server after fallback
(Heikki Linnakangas)
</para>
</listitem>
paralelism.patch (text/x-patch, 632B) downloaddiff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgmlindex b51826d..4ab073b 100644--- a/doc/src/sgml/config.sgml+++ b/doc/src/sgml/config.sgml@@ -3460,7 +3460,7 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
<listitem>
<para>
Maximum number of synchronization workers per subscription. This
- parameter controls the amount of paralelism of the initial data copy+ parameter controls the amount of parallelism of the initial data copy
during the subscription initialization or when new tables are added.
</para>
<para>
readded.patch (text/x-patch, 1.2K) downloaddiff --git a/doc/src/sgml/release-7.4.sgml b/doc/src/sgml/release-7.4.sgmlindex 1ddab66..88578dc 100644--- a/doc/src/sgml/release-7.4.sgml+++ b/doc/src/sgml/release-7.4.sgml@@ -4254,7 +4254,7 @@ DROP SCHEMA information_schema CASCADE;
The Python language no longer supports a restricted execution
environment, so the trusted version of PL/Python was removed. If
this situation changes, a version of PL/Python that can be used
- by non-superusers will be readded.+ by non-superusers will be read.
</para>
</listitem>
diff --git a/src/bin/pg_dump/pg_dump.c b/src/bin/pg_dump/pg_dump.cindex b26358c..c2eaa11 100644--- a/src/bin/pg_dump/pg_dump.c+++ b/src/bin/pg_dump/pg_dump.c@@ -9595,7 +9595,7 @@ dumpExtension(Archive *fout, ExtensionInfo *extinfo)
/*
* We unconditionally create the extension, so we must drop it if it
* exists. This could happen if the user deleted 'plpgsql' and then
- * readded it, causing its oid to be greater than g_last_builtin_oid.+ * read it, causing its oid to be greater than g_last_builtin_oid.
* The g_last_builtin_oid test was kept to avoid repeatedly dropping
* and recreating extensions like 'plpgsql'.
*/
transcations.patch (text/x-patch, 808B) downloaddiff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgmlindex 65a64c8..fe1e0ed 100644--- a/doc/src/sgml/maintenance.sgml+++ b/doc/src/sgml/maintenance.sgml@@ -594,7 +594,7 @@ SELECT datname, age(datfrozenxid) FROM pg_database;
scans every page in the table that is not already all-frozen, it should
set <literal>age(relfrozenxid)</> to a value just a little more than the
<varname>vacuum_freeze_min_age</> setting
- that was used (more by the number of transcations started since the+ that was used (more by the number of transactions started since the
<command>VACUUM</> started). If no <structfield>relfrozenxid</>-advancing
<command>VACUUM</> is issued on the table until
<varname>autovacuum_freeze_max_age</> is reached, an autovacuum will soon
updateable.patch (text/x-patch, 2.5K) downloaddiff --git a/doc/src/sgml/release-7.4.sgml b/doc/src/sgml/release-7.4.sgmlindex bc4f4e1..1ddab66 100644--- a/doc/src/sgml/release-7.4.sgml+++ b/doc/src/sgml/release-7.4.sgml@@ -4506,7 +4506,7 @@ DROP SCHEMA information_schema CASCADE;
<title>JDBC Changes</title>
<itemizedlist>
- <listitem><para>Allow <function>setNull</function> on updateable result sets</para></listitem>+ <listitem><para>Allow <function>setNull</function> on updatable result sets</para></listitem>
<listitem><para>Allow <function>executeBatch</function> on a prepared statement (Barry)</para></listitem>
<listitem><para>Support SSL connections (Barry)</para></listitem>
<listitem><para>Handle schema names in result sets (Paul Sorenson)</para></listitem>
diff --git a/doc/src/sgml/release-old.sgml b/doc/src/sgml/release-old.sgmlindex d4de6b1..625874c 100644--- a/doc/src/sgml/release-old.sgml+++ b/doc/src/sgml/release-old.sgml@@ -1228,7 +1228,7 @@ operations on bytea columns (Joe)</para></listitem>
<listitem><para>plpython used wrong value of <envar>atttypmod</envar> (Brad McLean)</para></listitem>
<listitem><para>Fix improper quoting of boolean values in Python interface (D'Arcy)</para></listitem>
<listitem><para>Added <function>addDataType()</function> method to PGConnection interface for JDBC</para></listitem>
-<listitem><para>Fixed various problems with updateable ResultSets for JDBC (Shawn Green)</para></listitem>+<listitem><para>Fixed various problems with updatable ResultSets for JDBC (Shawn Green)</para></listitem>
<listitem><para>Fixed various problems with DatabaseMetaData for JDBC (Kris Jurka, Peter Royal)</para></listitem>
<listitem><para>Fixed problem with parsing table ACLs in JDBC</para></listitem>
<listitem><para>Better error message for character set conversion problems in JDBC</para></listitem>
@@ -1874,7 +1874,7 @@ operations on bytea columns (Joe)</para></listitem>
<listitem><para>Add JDBC 3 support (Barry)</para></listitem>
<listitem><para>Allows JDBC to set loglevel by adding ?loglevel=X to the connection URL (Barry)</para></listitem>
<listitem><para>Add Driver.info() message that prints out the version number (Barry)</para></listitem>
-<listitem><para>Add updateable result sets (Raghu Nidagal, Dave)</para></listitem>+<listitem><para>Add updatable result sets (Raghu Nidagal, Dave)</para></listitem>
<listitem><para>Add support for callable statements (Paul Bethe)</para></listitem>
<listitem><para>Add query cancel capability</para></listitem>
<listitem><para>Add refresh row (Dave)</para></listitem>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: exclusion@gmail.com
Subject: Re: Fix some typos
In-Reply-To: <374e84e6-f89b-4d0a-652c-cb2449f0bfc4@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox