Re: preventing encoding conversion while starting up

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 18:09:43
Message-ID: 1027015783.8979.3.camel@taru.tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2002-07-18 at 18:57, Tom Lane wrote:
> Hannu Krosing <hannu(at)tm(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message J. R. Nield 2002-07-18 18:33:55 Re: Issues Outstanding for Point In Time Recovery (PITR)
Previous Message Tom Lane 2002-07-18 18:01:42 heap_delete, heap_mark4update must reset t_ctid