| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_ctl reports succes when start fails |
| Date: | 2003-10-27 16:44:02 |
| Message-ID: | 29994.1067273042@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-hackers-win32 |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> We can also try to come up with a better scheme for verifying that we
> have started properly - I will think about that.
There have been previous suggestions for a "pg_ping" functionality, in
which you could simply send a packet to the postmaster and it would
answer back if it's open for business. You can approximate this by
sending a deliberately invalid login packet, but it's not quite the same
thing. I think there were some concerns about security though; check
the archives.
In any case, a C-code pg_ctl could eliminate most of the problems
directly, simply because it wouldn't have to rely on psql.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-10-27 16:51:30 | Re: Help!!! FreeSpaceMap hashtalble out of memory. |
| Previous Message | Bruce Momjian | 2003-10-27 16:05:58 | Re: Still a few flaws in configure's default CFLAGS selection |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2003-10-27 19:03:39 | Re: pg_ctl reports succes when start fails |
| Previous Message | Michael Brusser | 2003-10-27 16:03:26 | Re: Defaults for GUC variables (was Re: pg_ctl reports |