| From: | Palle Girgensohn <girgen(at)pingpong(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | John Hansen <john(at)geeknet(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Patch for collation using ICU |
| Date: | 2005-03-25 21:06:52 |
| Message-ID: | A3649C58237C3A76B0EC332A@palle.girgensohn.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--On fredag, mars 25, 2005 09.53.38 -0500 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
wrote:
> Palle Girgensohn <girgen(at)pingpong(dot)net> writes:
>> hmm... I think I might have made a false assumption that
>> the locale string would contain the character encoding.
>
> You certainly cannot assume that. Would that it were so easy to find
> out the character set for a locale :-(.
>
> There's some code in initdb that you might emulate, though I can't say
> that I trust it a whole lot.
Best thing would of course be to check the encoding of the database. I
realized I've made a bad assumption that the initdb locale has anything to
do with the character encoding of the database - it doesn't. There must be
some already existsing trusted way to get the character encoding of a
database?
/Palle
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew T. O'Connor | 2005-03-25 21:12:27 | Re: lazy_update_relstats considered harmful (was Re: [PERFORM] |
| Previous Message | Matthew T. O'Connor | 2005-03-25 21:04:25 | Re: pg_autovacuum not having enough suction ? |