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.



Attachment: cannot.patch
Description: Binary data

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to