| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: nls and server log |
| Date: | 2014-12-30 01:40:12 |
| Message-ID: | 54A2027C.7070708@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/30/2014 06:39 AM, Jim Nasby wrote:
>>
>
> How much of this issue is caused by trying to machine-parse log files?
> Is a better option to improve that case, possibly doing something like
> including a field in each line that tells you the encoding for that entry?
That'd be absolutely ghastly. You couldn't just view the logs with
'less' or a text editor if your logs had mixed encodings, you'd need
some kind of special PostgreSQL log viewer tool.
Why would we possibly do that when we could just emit utf-8 instead?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2014-12-30 01:56:17 | Re: Detecting backend failures via libpq / DBD::Pg |
| Previous Message | Stephen Frost | 2014-12-30 01:34:36 | Re: CATUPDATE confusion? |