| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| 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 16:18:26 |
| Message-ID: | 1027009106.8551.16.camel@taru.tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tony Reina | 2002-07-18 16:56:45 | Re: Planner very slow on same query to slightly |
| Previous Message | Bruce Momjian | 2002-07-18 15:33:29 | Re: regression in CVS HEAD |