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 www.2ndQuadrant.com PostgreSQL Training, Services and Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
