From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | New pg_ctl has retrogressed in error messages |
Date: | 2004-05-31 17:14:19 |
Message-ID: | 1227.1086023659@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
7.4, on not finding a postmaster:
[tgl(at)rh1 pgsql]$ pg_ctl stop
/home/tgl/version74/bin/pg_ctl: line 274: kill: (15273) - No such process
waiting for postmaster to shut down................................................................ failed
pg_ctl: postmaster does not shut down
CVS tip, same scenario:
[tgl(at)rh1 pgsql]$ pg_ctl stop
stop signal failed
Not waiting for the results of a failed kill() is good, but the error
message is exceedingly unhelpful. It should mention the PID it tried to
kill and give the errno string. Perhaps
failed to signal postmaster process 15273: No such process
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-05-31 17:56:59 | Re: [HACKERS] New pg_ctl has retrogressed in error messages |
Previous Message | Tom Lane | 2004-05-31 16:48:20 | Re: Can't detect time zone |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-05-31 17:56:59 | Re: [HACKERS] New pg_ctl has retrogressed in error messages |
Previous Message | Bruce Momjian | 2004-05-31 13:37:36 | Re: pg_dump --comment? |