Yes, it does it consistently.
Maybe I should start from scratch, if this seems very broken.
Drew.
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Tom Lane
Sent: Sunday, April 24, 2005 11:02 AM
To: Simpson
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] postmaster stop hangs
"Simpson" <asimpson@i-55.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