| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Eugene Podshivalov <yaugenka(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15772: Some messages in log files are in ANSI encoding while server encoding is UTF8 |
| Date: | 2019-04-18 16:20:56 |
| Message-ID: | 12140.1555604456@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> I suppose you have databases with the single-byte encoding amidst your
> UTF8 ones. AFAIK the log file registers the log entries in the same
> encoding that the database uses. Different databases can use different
> encodings.
> That's pretty broken, but it's how it is.
Yeah, and it's not easy to improve on. If we tried to convert all
log messages to the same encoding, which one would that be?
(Please, no nonsense about UTF8 being a universal solution.
The Japanese don't think so, for instance.)
Also, what do you do if you get an encoding conversion failure?
That's even before you get into implementation-dependent problems,
like what to do early in process startup before the encoding
conversion machinery is operational.
A more realistic idea might be to have separate log files for
different encodings, though that has a bunch of management issues
to solve as well.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eugene Podshivalov | 2019-04-18 16:26:50 | Re: BUG #15772: Some messages in log files are in ANSI encoding while server encoding is UTF8 |
| Previous Message | Alvaro Herrera | 2019-04-18 16:01:16 | Re: BUG #15772: Some messages in log files are in ANSI encoding while server encoding is UTF8 |