| From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 11:23:50 |
| Message-ID: | 48734E46.7080907@sun.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout napsal(a):
>
> Oh I see, you're referring to the storage of the default collation for
> a database. I was jumping ahead to the per-column collation state, when
> the collation default is attached to columns, types and domains, and
> not at the database level. So there the problem does not exist.
Yeah, but you still need one source/one collation list for database, scheme,
table and column. And of course shared tables need also collation for their indexes.
> To be honest, I'd suggest storing the collation in pg_database as a
> string, rather than as an identifier. This sidesteps the problem
> entirly.
I don't think that string is good idea. You need to use same approach on all
levels by my opinion.
Zdenek
--
Zdenek Kotala Sun Microsystems
Prague, Czech Republic http://sun.com/postgresql
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-07-08 12:16:31 | Re: [PATCHES] WIP: executor_hook for pg_stat_statements |
| Previous Message | Martijn van Oosterhout | 2008-07-08 10:19:18 | Re: [WIP] patch - Collation at database level |