Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement
Date
Msg-id 9500.1321568969@sss.pgh.pa.us
Whole thread Raw
In response to Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Nov 17, 2011 at 4:26 PM, Alvaro Herrera
> <alvherre@commandprompt.com> wrote:
>> So the buildfarm broke due to this change, because citext does

> Thanks for fixing it.  Should we revert the original change?

I still think it's reasonable to remove the extra downcasing step,
but we'll have to document it as a change.  For instance, spelling
C as either "C" or 'C' would work differently now.  The fact that
the former is downcased seems quite surprising to me, so I don't
think anybody would say that this isn't a better definition, but
undoubtedly it could force people to change their source files.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Rudyar
Date:
Subject: Re: how to get tuple
Next
From: Josh Kupershmidt
Date:
Subject: Re: psql + libedit command history truncation (was: psql history vs. dearmor (pgcrypto))