On 22/09/2010 9:41 PM, Tom Lane wrote:
Craig Ringer writes:
On 22/09/2010 5:45 PM, Peter Eisentraut wrote:
We need to produce the log output in the server encoding, because that's
how we need to send it to the client.
That doesn't mean it can't be recoded for writing to the log file,
though
On 09/22/2010 09:55 PM, Tom Lane wrote:
Peter Eisentraut writes:
On ons, 2010-09-22 at 19:25 +0800, Craig Ringer wrote:
I still wonder if, rather than making this configurable, the right
choice is to force logging to UTF-8 (with BOM) across the board,
I don't think this would make things be
Hi Craig,
Almost Japanese software emit log files by encoding of the server the
software running on. I'm not sure it is the best way or not, but
Japanese users taking it for granted.
So I feel that Japanese users would hope that postgre server has same
style with other software, cause many adminis
Peter Eisentraut writes:
> On ons, 2010-09-22 at 19:25 +0800, Craig Ringer wrote:
>> I still wonder if, rather than making this configurable, the right
>> choice is to force logging to UTF-8 (with BOM) across the board,
> I don't think this would make things better or easier. At some point
> yo
Craig Ringer writes:
> On 22/09/2010 5:45 PM, Peter Eisentraut wrote:
>> We need to produce the log output in the server encoding, because that's
>> how we need to send it to the client.
> That doesn't mean it can't be recoded for writing to the log file,
> though. Perhaps it needs to be. It sho
On ons, 2010-09-22 at 19:25 +0800, Craig Ringer wrote:
> Yep, I tend to think that'd be the right way to go. It'd still be a bit
> of a pain, though, as messages written to stdout/stderr by the
> postmaster should be in the system encoding, but messages written to the
> log files should be in th
On Wed, Sep 22, 2010 at 12:25 PM, Craig Ringer
wrote:
> I don't think that's an OK answer, myself. Mixed encodings with no
> delineation in one file = bug as far as I'm concerned. You can't even rely
> on being able to search the log anymore. You'll only get away with it when
> using languages tha
On 22/09/2010 5:45 PM, Peter Eisentraut wrote:
On ons, 2010-09-22 at 16:25 +0800, Craig Ringer wrote:
A single log file should obviously be in a single encoding, it's the
only sane way to do things. But which encoding is it in? And which
*should* it be in?
We need to produce the log output in
On ons, 2010-09-22 at 16:25 +0800, Craig Ringer wrote:
> A single log file should obviously be in a single encoding, it's the
> only sane way to do things. But which encoding is it in? And which
> *should* it be in?
We need to produce the log output in the server encoding, because that's
how we ne
[moving to pgsql-hackers; this isn't the simple bug I initially
suspected it might be]
On 20/09/10 03:10, Tom Lane wrote:
> Craig Ringer writes:
>> One of the correctly encoded messages is "Unexpected EOF received on
>> client connection"
>
>> One of the incorrectly encoded (shift-JIS) messages
10 matches
Mail list logo
