Skip site navigation (1) Skip section navigation (2)

Re: main log encoding problem

From: Alexander Law <exclusion(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: 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: main log encoding problem
Date: 2012-07-19 09:33:01
Message-ID: 5007D44D.9030904@gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-generalpgsql-hackers
>> 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).
> So, what you wanted to say here is:
>
> "If the conversion to this encoding is not avaliable then fall back to
> UTF-8"
>
> Am I correct?
>
> Also is it possible to completely disable the feature?
>
Yes, you're.  I think it could be disabled by setting log_encoding='', 
but if the parameter is missing then the feature should be enabled (with 
UTF-8).



In response to

pgsql-hackers by date

Next:From: Andres FreundDate: 2012-07-19 10:29:03
Subject: [PATCH] XLogReader v2
Previous:From: Kohei KaiGaiDate: 2012-07-19 09:06:21
Subject: Re: pgsql_fdw in contrib

pgsql-bugs by date

Next:From: Alexander LawDate: 2012-07-19 11:50:44
Subject: Re: [GENERAL] main log encoding problem
Previous:From: Alban HertroysDate: 2012-07-19 09:01:49
Subject: Re: [GENERAL] main log encoding problem

pgsql-general by date

Next:From: Edson RichterDate: 2012-07-19 11:35:29
Subject: Synchronization Master -> Slave
Previous:From: younusDate: 2012-07-19 09:17:59
Subject: Re: How to stop a query

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group