| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Gregory Stark <stark(at)enterprisedb(dot)com>, Radek Strnad <radek(dot)strnad(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP patch: Collation support |
| Date: | 2008-09-23 11:26:32 |
| Message-ID: | 48D8D268.2080305@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zdenek Kotala wrote:
> pg_collation catalog is also important for pg_dump, because system
> collation names are not compatible over OS and pg_dump output should be
> portable. pg_collation adds abstract layer which solve this problem.
That's a valid point. We'll still need a way to map OS locale to
whatever internal names we invent for them, though, so I'm not sure if
the pg_collation catalog helps much, but just moves the problem
elsewhere. The pg_dump output of the CREATE COLLATION statements still
wouldn't be portable from one OS to another.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-09-23 12:14:58 | Re: pg_type.h regression? |
| Previous Message | Zdenek Kotala | 2008-09-23 11:19:35 | Re: WIP patch: Collation support |