| 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 08:40:34 |
| Message-ID: | 5007C802.3060007@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general pgsql-hackers |
>> 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).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2012-07-19 08:54:36 | Re: main log encoding problem |
| Previous Message | Tatsuo Ishii | 2012-07-19 08:28:05 | Re: main log encoding problem |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2012-07-19 08:54:36 | Re: main log encoding problem |
| Previous Message | Tatsuo Ishii | 2012-07-19 08:28:05 | Re: main log encoding problem |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2012-07-19 08:54:36 | Re: main log encoding problem |
| Previous Message | Tatsuo Ishii | 2012-07-19 08:28:05 | Re: main log encoding problem |