| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, tkbysh2000(at)yahoo(dot)co(dot)jp, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: BUG #5661: The character encoding in logfile is confusing. |
| Date: | 2010-09-22 09:45:22 |
| Message-ID: | 1285148722.15691.19.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On ons, 2010-09-22 at 16:25 +0800, Craig Ringer wrote:
> A single log file should obviously be in a single encoding, it's the
> only sane way to do things. But which encoding is it in? And which
> *should* it be in?
We need to produce the log output in the server encoding, because that's
how we need to send it to the client. If you have different databases
with different server encodings, you will get inconsistently encoded
output in the log file.
Conceivably, we could create a configuration option that specifies the
encoding for the log file, and strings a recoded from whatever gettext()
produces to the specified encoding. initdb could initialize that option
suitably, so in most cases users won't have to do anything.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2010-09-22 11:25:47 | Re: BUG #5661: The character encoding in logfile is confusing. |
| Previous Message | Craig Ringer | 2010-09-22 08:25:33 | Re: BUG #5661: The character encoding in logfile is confusing. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Björklund | 2010-09-22 10:03:47 | Documentation, window functions |
| Previous Message | subham | 2010-09-22 09:30:01 | Re: Needs Suggestion |