From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: eric.mutta@gmail.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Typo in description of PROGRAM parameter for the COPY command
Date: Sun, 21 Aug 2022 15:14:21 -0400
Message-ID: <4173834.1661109261@sss.pgh.pa.us> (raw)
In-Reply-To: <C032C9AB-21E4-440C-ADC8-9AC7412C3D19@yesql.se>
References: <166104548566.654.11680826843612576896@wrigleys.postgresql.org>
<1DC6647E-45CF-4ECD-BAB5-0CC0626AF121@yesql.se>
<4169601.1661107714@sss.pgh.pa.us>
<C032C9AB-21E4-440C-ADC8-9AC7412C3D19@yesql.se>
Daniel Gustafsson <daniel@yesql.se> writes:
> Skimming the page I noticed that we wrap CSV in <literal/> in all but a few
> places, which seemed randomly "chosen". Another sentence which stood out to me
> was this one on FREEZE:
> "This violates the normal rules of MVCC visibility and users specifying
> should be aware of the potential problems this might cause."
> The use of "specifying" seems odd to me, removing it makes it read clearer
> IM-non-native-O.
I suppose the author was aiming at "specifying it", but I agree that
just dropping "specifying" works fine with fewer words.
> The attached includes all the above suggestions.
LGTM.
regards, tom lane
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: tgl@sss.pgh.pa.us, daniel@yesql.se, eric.mutta@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Typo in description of PROGRAM parameter for the COPY command
In-Reply-To: <4173834.1661109261@sss.pgh.pa.us>
* 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