Re: preventing encoding conversion while starting up

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hannu Krosing <hannu(at)tm(dot)ee>
Cc: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: preventing encoding conversion while starting up
Date: 2002-07-18 22:21:35
Message-ID: 2802.1027030895@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hannu Krosing <hannu(at)tm(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-07-18 22:35:37 Re: compiler warnings from cvs tip
Previous Message Joe Conway 2002-07-18 22:12:53 Re: RFC: listing lock status