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

From Hannu Krosing
Subject Re: preventing encoding conversion while starting up
Date
Msg-id 1027015783.8979.3.camel@taru.tm.ee
Whole thread Raw
In response to Re: preventing encoding conversion while starting up  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: preventing encoding conversion while starting up  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2002-07-18 at 18:57, Tom Lane wrote:
> Hannu Krosing <hannu@tm.ee> writes:
> > Why can't we just open the listening socket _after_ the database has
> > completed starting up phase ?
> 
> 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 ?

-----------
Hannu



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: regression in CVS HEAD
Next
From: Tom Lane
Date:
Subject: heap_delete, heap_mark4update must reset t_ctid