Re: [PGdocs] fix description for handling pf non-ASCII characters

From: "Karl O(dot) Pinc" <kop(at)karlpinc(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, 'jian he' <jian(dot)universality(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PGdocs] fix description for handling pf non-ASCII characters
Date: 2023-09-26 21:50:20
Message-ID: e2a148d9-3f2c-4a86-b493-35c41ed75e93@karlpinc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sep 26, 2023 1:10:55 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> "Karl O. Pinc" <kop(at)karlpinc(dot)com> writes:
>> For the last hunk you'd change around "anything".  Write:
>> "... it will be truncated to less than NAMEDATALEN characters and
>> the bytes of the string which are not printable ASCII characters ...".
>
>> Notice that I have also changed "that" to "which" just above. 
>> I _think_ this is better English.
>
> No, I'm pretty sure you're mistaken.  It's been a long time since
> high school English, but the way I think this works is that "that"
> introduces a restrictive clause, which narrows the scope of what
> you are saying.  That is, you say "that" when you want to talk
> about only the bytes of the string that aren't ASCII.  But "which"
> introduces a non-restrictive clause that adds information or
> commentary.  If you say "bytes of the string which are not ASCII",
> you are effectively making a side assertion that no byte of the
> string is ASCII.  Which is not the meaning you want here.

Makes sense to me.  "That" it is.

Thanks for the help. I never would have figured that out.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-09-26 21:50:29 Re: dikkop seems unhappy because of openssl stuff (FreeBSD 14-BETA1)
Previous Message Bruce Momjian 2023-09-26 21:42:13 Re: [PATCH] pgrowlocks: Make mode names consistent with docs