Re: preventing encoding conversion while starting up - Mailing list pgsql-hackers

From Tom Lane
Subject Re: preventing encoding conversion while starting up
Date
Msg-id 2802.1027030895@sss.pgh.pa.us
Whole thread Raw
In response to Re: preventing encoding conversion while starting up  (Hannu Krosing <hannu@tm.ee>)
Responses Re: preventing encoding conversion while starting up  (Hannu Krosing <hannu@tm.ee>)
Re: preventing encoding conversion while starting up  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
Hannu Krosing <hannu@tm.ee> writes:
> On Thu, 2002-07-18 at 18:57, Tom Lane wrote:
>> The problem is not just there.  The real problem is that with this patch
>> installed, it is impossible to report startup errors of any kind,
>> because the client communication mechanism now depends on having working
>> database access.  I regard this as a fatal problem :-(

> So the right way would be to always start up in us-ascii (7-bit) and
> re-negotiate encodings later ?

That might be one way out ... but doesn't it mean breaking the wire
protocol?  Existing clients aren't likely to know to do that.

It seems like we've collected enough reasons for a protocol change that
one might happen for 7.4.  I'd rather not have it happen in 7.3, though,
because we don't have enough time left to address all the issues I'd
like to see addressed...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: RFC: listing lock status
Next
From: Tom Lane
Date:
Subject: Re: compiler warnings from cvs tip