| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Locale, Collation, ICU patch |
| Date: | 2008-04-03 19:23:59 |
| Message-ID: | 47F52ECF.4050304@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> The other issue that'd have to be resolved is the problem of system log
> output. I think we'd wish that log messages are written in a uniform
> encoding (CSV output in particular is going to have a hard time
> otherwise) but what do you do when you need to report something that
> includes a character not present in that encoding?
>
>
>
I think the only problem with CSV logs would be in trying to read them
back into Postgres (which I agree is the main point of having them).
We need to be more aggressive about dealing with these problems, or else
how will we ever get to per-column charsets/collations?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-04-03 19:24:55 | Re: modules |
| Previous Message | Darcy Buskermolen | 2008-04-03 19:03:43 | Re: modules |