| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | cjames(at)emolecules(dot)com |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Punctuation error |
| Date: | 2018-09-19 14:43:25 |
| Message-ID: | 14262.1537368205@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
=?utf-8?q?PG_Doc_comments_form?= <noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil | 2018-09-19 15:23:41 | Re: Punctuation error |
| Previous Message | Michael Paquier | 2018-09-19 02:53:02 | Re: Mention FK creation take ShareRowExclusiveLock on referenced table |