Re: Cannot - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Cannot
Date
Msg-id 13D9C88D-7A78-4586-8A46-C92ECF335BF9@kineticode.com
Whole thread Raw
In response to Re: Cannot  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Oct 26, 2011, at 2:58 PM, Tom Lane wrote:

>> I read this as equivalent to "can be not released." Which of course is silly, so as I read it I realize what it
means,but it trips up my overly logical brain. It interrupts the flow. There is no such confusion in "cannot be
released"and thus no tripping up on meaning. 
>
> This particular change seems like an improvement to me, but it's hardly
> an adequate argument for a global search-and-replace.  There might be
> other places where such a change renders things *less* readable.

The patch is actually quite modest; there are only a few instances of "can not". Attached.

Best,

David


Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Cannot
Next
From: Florian Pflug
Date:
Subject: Re: Hot Backup with rsync fails at pg_clog if under load