From: | Marvin Solomon <solomon(at)cs(dot)wisc(dot)edu> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | follow-up: problems with pg_ctl -w |
Date: | 2007-01-10 15:49:00 |
Message-ID: | 45A50AEC.8000204@cs.wisc.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-patches |
[This is meant to be a follow-up of a bug report I sent earlier using the web
form. It's not clear to me the right way to post a follow-up, since I didn't
get a copy of the email generated by the web form, and the email hasn't shown
up on the pgsql-bugs web site -- at least not yet.]
I subsequently discovered that setting PGUSER in the environment gets around
the first problem I mentioned, so it's really just a documentation problem:
PGUSER is not mentioned on the pg_ctl doc page.
But I found a worse problem. Sometimes (not repeatably), pg_ctl start -w
logs the message
FATAL: the database is starting up
and immediately returns. I believe the correct thing for it to do when it
gets this message from an attempt to open a session is to try again. Instead,
it returns as if the startup was successful.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-01-10 16:38:20 | Re: [pgsql-patches] xlog lockup patch (was: BUG #2712: |
Previous Message | Ravalison Frederyk | 2007-01-10 13:00:50 | BUG #2877: Caused by: org.postgresql.util.PSQLException: Unknown Response Type |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-01-10 16:22:11 | Re: [HACKERS] [PATCHES] Last infomask bit |
Previous Message | Tom Lane | 2007-01-10 15:37:56 | Re: [PATCHES] COPY with no WAL, in certain circumstances |