From: Tom Lane <tgl@sss.pgh.pa.us>
To: cjames@emolecules.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Punctuation error
In-reply-to: <153731137094.14990.16664858806045765740@wrigleys.postgresql.org>
References: <153731137094.14990.16664858806045765740@wrigleys.postgresql.org>
Comments: In-reply-to =?utf-8?q?PG_Doc_comments_form?=
 <noreply@postgresql.org>
	message dated "Tue, 18 Sep 2018 22:56:10 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <14261.1537368205.1@sss.pgh.pa.us>
Date: Wed, 19 Sep 2018 10:43:25 -0400
Message-ID: <14262.1537368205@sss.pgh.pa.us>
Precedence: bulk

=?utf-8?q?PG_Doc_comments_form?= <noreply@postgresql.org> writes:
> This sentence should not use a semicolon: "Both the ADD TABLE and DROP TABLE
> operations are transactional; so the table will start or stop replicating at
> the correct snapshot once the transaction has committed."

That looks perfectly fine to me.  Moreover, there are a *lot* of places
in the PG docs that we'd have to change if we got persnickety about this
sort of thing.

> You can either
> change it to a comma, or else leave out the "so" that follows the semicolon.
> The text that follows a semicolon must be a complete sentence that stands on
> its own.

I am unfamiliar with this grammar "rule", and vigorously dispute that
anyone follows it in the real world.

			regards, tom lane