Re: [GENERAL] main log encoding problem

From: Alban Hertroys <haramrae(at)gmail(dot)com>
To: Alexander Law <exclusion(at)gmail(dot)com>
Cc: Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-general(at)postgresql(dot)org, ringerc(at)ringerc(dot)id(dot)au, yi(dot)codeplayer(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: [GENERAL] main log encoding problem
Date: 2012-07-19 09:01:49
Message-ID: CAF-3MvNJvMzFO9=UDqi9RB3qAJWhEMOVM4kKF3bRswNSNaAm3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general pgsql-hackers

Yikes, messed up my grammar a bit I see!

On 19 July 2012 10:58, Alban Hertroys <haramrae(at)gmail(dot)com> wrote:

> I like Craig's idea of adding the client encoding to the log lines. A
> possible problem with that (I'm not an encoding expert) is that a log
> line like that will contain data about the database server meta-data
> (log time, client encoding, etc) in the database default encoding and

...will contain meta-data about the database server (log time...

> It appears that the primarly here is that SQL statements and

It appears the primary issue here...

--
If you can't see the forest for the trees,
Cut the trees and you'll see there is no forest.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Law 2012-07-19 09:33:01 Re: main log encoding problem
Previous Message Alban Hertroys 2012-07-19 08:58:42 Re: [GENERAL] main log encoding problem

Browse pgsql-general by date

  From Date Subject
Next Message younus 2012-07-19 09:17:59 Re: How to stop a query
Previous Message Alban Hertroys 2012-07-19 08:58:42 Re: [GENERAL] main log encoding problem

Browse pgsql-hackers by date

  From Date Subject
Next Message Kohei KaiGai 2012-07-19 09:06:21 Re: pgsql_fdw in contrib
Previous Message Alban Hertroys 2012-07-19 08:58:42 Re: [GENERAL] main log encoding problem