Re: [WIP] patch - Collation at database level

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Gregory Stark <stark(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Radek Strnad <radek(dot)strnad(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [WIP] patch - Collation at database level
Date: 2008-07-08 16:42:55
Message-ID: 4873990F.1090307@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane napsal(a):
> Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
>> ... And of course shared tables need also collation for their indexes.
>
> No, they don't, because the only textual indexes on shared catalogs are
> on "name" columns, which are intentionally not locale aware, and
> wouldn't be collation aware either.

Yeah, name uses strcmp, which is not locale aware but from ANSI perspective
there is collation SQL_IDENTIFIER for it which is fortunately implementation
defined.

What I see now as the problem is that we need also to know correct collation for
ORDER - for example:

select * from pg_shdescription order by description;

...thinking...

but it should solve by collation per column which will work well with
pg_attribute cloning for new database as Martijn mentioned.

Zdenek

--
Zdenek Kotala Sun Microsystems
Prague, Czech Republic http://sun.com/postgresql

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2008-07-08 16:44:57 Re: Proposal of SE-PostgreSQL patches [try#2]
Previous Message Josh Berkus 2008-07-08 16:35:32 Re: [PATCHES] Solaris ident authentication using unix domain sockets