Re: [HACKERS] [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.

2016-10-03 Thread Robert Haas
On Mon, Oct 3, 2016 at 3:33 PM, Kevin Grittner wrote: >> Anyway, we've probably beaten this horse to death. > > Just to be sure of that, I'll cite the Chicago Manual of Style (my > preferred style guide), which seems to chart a course somewhere in > the middle: > > http://www.chicagomanualofstyle.

Re: [HACKERS] [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.

2016-10-03 Thread Kevin Grittner
On Mon, Oct 3, 2016 at 9:22 AM, Tom Lane wrote: > Robert Haas writes: >> Sure, I'm not arguing with trying to be formal. The grammatical rule >> that you're describing doesn't exist for me, though. I believe that >> "that" can only introduce a restrictive clause, whereas "which" can >> introduc

Re: [HACKERS] [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.

2016-10-03 Thread Tom Lane
Robert Haas writes: > Sure, I'm not arguing with trying to be formal. The grammatical rule > that you're describing doesn't exist for me, though. I believe that > "that" can only introduce a restrictive clause, whereas "which" can > introduce either a descriptive or a restrictive clause. Yeah,

Re: [HACKERS] [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.

2016-10-03 Thread Robert Haas
On Mon, Oct 3, 2016 at 8:51 AM, Tom Lane wrote: > Robert Haas writes: >> Why do you keep insisting on changing case where I've written "which" >> to instead say "that" in situations where AFAIK either is perfectly >> correct? I find such changes at best neutral, and in some cases >> worse. > > W

Re: [HACKERS] [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.

2016-10-03 Thread Tom Lane
Robert Haas writes: > Why do you keep insisting on changing case where I've written "which" > to instead say "that" in situations where AFAIK either is perfectly > correct? I find such changes at best neutral, and in some cases > worse. What I was taught in school was that "that" introduces a re

Re: [HACKERS] [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.

2016-10-02 Thread Michael Paquier
On Mon, Oct 3, 2016 at 11:06 AM, Robert Haas wrote: > On Sun, Oct 2, 2016 at 9:00 PM, Thomas Munro > wrote: >> On Mon, Oct 3, 2016 at 1:36 PM, Robert Haas wrote: >>> On Sat, Oct 1, 2016 at 3:33 PM, Tom Lane wrote: Copy-editing for contrib/pg_visibility documentation. Add omitted

Re: [HACKERS] [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.

2016-10-02 Thread Robert Haas
On Sun, Oct 2, 2016 at 9:00 PM, Thomas Munro wrote: > On Mon, Oct 3, 2016 at 1:36 PM, Robert Haas wrote: >> On Sat, Oct 1, 2016 at 3:33 PM, Tom Lane wrote: >>> Copy-editing for contrib/pg_visibility documentation. >>> >>> Add omitted names for some function parameters. >>> Fix some minor grammat

Re: [HACKERS] [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.

2016-10-02 Thread Thomas Munro
On Mon, Oct 3, 2016 at 1:36 PM, Robert Haas wrote: > On Sat, Oct 1, 2016 at 3:33 PM, Tom Lane wrote: >> Copy-editing for contrib/pg_visibility documentation. >> >> Add omitted names for some function parameters. >> Fix some minor grammatical issues. > > Why do you keep insisting on changing case

Re: [HACKERS] [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.

2016-10-02 Thread Robert Haas
On Sat, Oct 1, 2016 at 3:33 PM, Tom Lane wrote: > Copy-editing for contrib/pg_visibility documentation. > > Add omitted names for some function parameters. > Fix some minor grammatical issues. Why do you keep insisting on changing case where I've written "which" to instead say "that" in situation