| From: | "Simpson" <asimpson(at)i-55(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: postmaster stop hangs |
| Date: | 2005-04-25 11:49:08 |
| Message-ID: | NFBBKOADOLGDLPMAAHMDOEKLDCAA.asimpson@i-55.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Yes, it does it consistently.
Maybe I should start from scratch, if this seems very broken.
Drew.
-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org]On Behalf Of Tom Lane
Sent: Sunday, April 24, 2005 11:02 AM
To: Simpson
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] postmaster stop hangs
"Simpson" <asimpson(at)i-55(dot)com> writes:
> Here is a ps of the currently running instance:
> postgres 5671 1 0 02:32 pts/0 00:00:00
> /usr/local/pgsql/bin/postmaster -D /data/pgsql/data
> postgres 5674 5671 0 02:32 pts/0 00:00:00 postgres: writer process
> postgres 5675 5671 0 02:32 pts/0 00:00:00 postgres: stats buffer
> process
> postgres 5676 5675 0 02:32 pts/0 00:00:00 postgres: stats collector
> process
> 5676 is in the */data/postmaster.pid
That seems extremely broken. Can you reproduce this state (wrong PID in
postmaster.pid) after restarting the postmaster?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Browne | 2005-04-25 12:25:28 | Re: PL/SQL |
| Previous Message | lst_hoe01 | 2005-04-25 10:52:09 | Re: lots of idle connections open by application |