Re: preventing encoding conversion while starting up

On Thu, 2002-07-18 at 06:55, Tatsuo Ishii wrote:
> I have faced a problem with encoding conversion while the database is
> starting up. If postmaster accepts a connection request while in the
> state, it issues a fatal message "The database system is starting
> up". Then the encoding conversion system tries to convert the message
> to client encoding if neccessary (e.g. PGCLIENTENCODING is set for
> postmaster process). Then it calles recomputeNamespacePath() which
> calls GetUserId(), it ends up with an assersion error (see below).
> 
> To prevent this, I would like to add a public function to postmaster.c
> to know we are in the database starting up phase:

Why can't we just open the listening socket _after_ the database has
completed starting up phase ?

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