From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: preventing encoding conversion while starting up |
Date: | 2002-07-18 13:53:26 |
Message-ID: | 4979.1027000406@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> 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).
This seems to me to be a fatal objection to the entire concept of
storing encoding status in the database. If the low-level client
communication code needs to access that information, then the postmaster
is broken and is not repairable.
> To prevent this, I would like to add a public function to postmaster.c
> to know we are in the database starting up phase:
How will that help?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-07-18 13:55:22 | Re: Bright ideas required for drop column... |
Previous Message | Magnus Naeslund(f) | 2002-07-18 09:41:51 | [PATCH] Win32 native fixes after SSL updates (+more) |