On 07/19/2012 04:58 PM, Alban Hertroys wrote:
On 19 July 2012 10:40, Alexander Law <exclus...@gmail.com> wrote:
Ok, maybe the time of real universal encoding has not yet come. Then
we maybe just should add a new parameter "log_encoding" (UTF-8 by
default) to postgresql.conf. And to use this encoding consistently
within logging_collector.
If this encoding is not available then fall back to 7-bit ASCII.
What do you mean by "not available"?
Sorry, it was inaccurate phrase. I mean "if the conversion to this encoding
is not avaliable". For example, when we have database in EUC_JP and
log_encoding set to Latin1. I think that we can even fall back to UTF-8 as
we can convert all encodings to it (with some exceptions that you noticed).
I like Craig's idea of adding the client encoding to the log lines.
Nonono! Log *file* *names* when one-file-per-database is in use.
Encoding as a log line prefix is a terrible idea for all sorts of reasons.
--
Craig Ringer
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
