Re: main log encoding problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: exclusion(at)gmail(dot)com, 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 01:42:45
Message-ID: 7295.1342662165@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general pgsql-hackers

Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
> My idea is using mule-internal encoding for the log file instead of
> UTF-8. There are several advantages:

> 1) Converion to mule-internal encoding is cheap because no conversion
> table is required. Also no information loss happens in this
> conversion.

> 2) Mule-internal encoding can be handled by emacs, one of the most
> popular editors in the world.

> 3) No need to worry about locale. Mule-internal encoding has enough
> information about language.

Um ... but ...

(1) nothing whatsoever can read MULE, except emacs and xemacs.

(2) there is more than one version of MULE (emacs versus xemacs,
not to mention any possible cross-version discrepancies).

(3) from a log volume standpoint, this could be pretty disastrous.

I'm not for a write-only solution, which is pretty much what this
would be.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tatsuo Ishii 2012-07-19 01:57:27 Re: main log encoding problem
Previous Message Tatsuo Ishii 2012-07-18 23:16:26 Re: main log encoding problem

Browse pgsql-general by date

  From Date Subject
Next Message Tatsuo Ishii 2012-07-19 01:57:27 Re: main log encoding problem
Previous Message Adrian Klaver 2012-07-19 00:47:17 Re: Trouble with NEW

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2012-07-19 01:57:27 Re: main log encoding problem
Previous Message Tatsuo Ishii 2012-07-18 23:16:26 Re: main log encoding problem