Re: PostgreSQL Gotchas - Mailing list pgsql-general

From Jan Wieck
Subject Re: PostgreSQL Gotchas
Date
Msg-id 434FC20D.7020205@Yahoo.com
Whole thread Raw
In response to Re: PostgreSQL Gotchas  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PostgreSQL Gotchas
Re: PostgreSQL Gotchas
List pgsql-general
On 10/13/2005 2:40 PM, Tom Lane wrote:
> Chris Travers <chris@travelamericas.com> writes:
>> So basically, the problem is that any fix for case folding would touch a
>> fair bit of code and possibly cause other problems.  However, I haven't
>> seen anyone worry about performance issues in such a fix, just that it
>> might be a fair bit of work.
>
> More that it's likely to create serious forwards, backwards, and
> sideways compatibility problems :-(.  The work involved is mostly
> in figuring out how to deal with that.
>
> Since the end reward for all this work would be having to read CATALOGS
> WRITTEN IN ALL UPPER CASE, none of the key developers seem very
> interested ...

Just an idea ...

if the release that offers UPPER case folding as an option also makes
sure that all internal and tool references to system catalog objects are
properly quoted (as they IMHO should be anyway), then it would be
reduced to a third party tool/application problem accessing the system
catalog in a database that has this new config option selected.


Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #

pgsql-general by date:

Previous
From: han.holl@informationslogik.nl
Date:
Subject: Re: Postgres logs to syslog LOCAL0
Next
From: Andrew Sullivan
Date:
Subject: Re: On "multi-master"