| 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 |
| 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?
>
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).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Law | 2012-07-19 11:50:44 | Re: [GENERAL] main log encoding problem |
| Previous Message | Alban Hertroys | 2012-07-19 09:01:49 | Re: [GENERAL] main log encoding problem |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Edson Richter | 2012-07-19 11:35:29 | Synchronization Master -> Slave |
| Previous Message | younus | 2012-07-19 09:17:59 | Re: How to stop a query |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-07-19 10:29:03 | [PATCH] XLogReader v2 |
| Previous Message | Kohei KaiGai | 2012-07-19 09:06:21 | Re: pgsql_fdw in contrib |