| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | exclusion(at)gmail(dot)com |
| Cc: | 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: main log encoding problem |
| Date: | 2012-07-19 08:54:36 |
| Message-ID: | 20120719.175436.1062448769311172541.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general pgsql-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?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2012-07-19 08:58:42 | Re: [GENERAL] main log encoding problem |
| Previous Message | Alexander Law | 2012-07-19 08:40:34 | Re: main log encoding problem |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2012-07-19 08:58:42 | Re: [GENERAL] main log encoding problem |
| Previous Message | Alexander Law | 2012-07-19 08:40:34 | Re: main log encoding problem |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2012-07-19 08:58:42 | Re: [GENERAL] main log encoding problem |
| Previous Message | Alexander Law | 2012-07-19 08:40:34 | Re: main log encoding problem |