Re: Identifier case folding notes

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Identifier case folding notes
Date: 2008-07-08 17:47:13
Message-ID: 1215539233.4051.974.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, 2008-07-08 at 19:25 +0200, Peter Eisentraut wrote:
> 4. Compare the "name" data type in a case-insensitive manner. This
> would probably address most problem cases. Again, you can't have
> objects with names
> different in case only. One condition to implementing this would be
> that this
> behavior would have be tied down globally at initdb, because it
> affects system
> indexes and shared catalogs. That might be impractical for some,
> because
> you'd need different instances for different behaviors, especially
> when you
> want to host multiple applications or want to port an affected
> application to
> the native PostgreSQL behavior over time.

That sounds the most workable, given your descriptions.

If objects are never different solely by case alone, then you will have
the same index ordering as if you had sent them all to lower case.

Surely it is possible to mix the two approaches somehow?

Simon Riggs
PostgreSQL Training, Services and Support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-07-08 17:53:25 Re: Identifier case folding notes
Previous Message Andrew Dunstan 2008-07-08 17:34:01 Re: [PATCHES] Solaris ident authentication using unix domain sockets