Re: Typo in description of PROGRAM parameter for the COPY command

Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> On 21 Aug 2022, at 03:31, PG Doc comments form <noreply(at)postgresql(dot)org> wrote:
>> ...so if you need to pass any arguments to shell command that come
>> from an untrusted source...
>>
>> The "to shell command that come" part should be changed so it either reads
>> like this:
>>
>> ...so if you need to pass any arguments to a shell command that comes
>> from an untrusted source...
>>
>> ...or it reads like this:
>>
>> ...so if you need to pass any arguments to shell commands that come
>> from an untrusted source...

> Not being a native english speaker, but since we're already referring to "the
> command" in the sentence it seems more natural to me to change to "the shell
> command".

Hmm ... to me the main problem with this fragment is that it's not
entirely clear whether we're speaking of untrusted arguments or an
untrusted shell command, ie which one is the antecedent of "that".
The proposed variants seem to make that worse not better. I suggest
rephrasing like

... so if you need to include any shell command arguments that come from
an untrusted source, you must ...

Or maybe even better, just drop "shell command" from that phrase
altogether.

Probably also s/passing/including/ in the next sentence.

regards, tom lane