From: Jeff Frost <jeff@frostconsultingllc.com>
To: Carol Walter <walterc@indiana.edu>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Continuing issues... Can't vacuum!
Date: Fri, 23 May 2008 15:18:49 -0700
Message-ID: <483742C9.6000906@frostconsultingllc.com> (raw)
In-Reply-To: <4FAAB56B-864B-4B20-858A-4D5D0EA9E12E@indiana.edu>
References: <5897F703-1525-477B-8749-80A0A4E0A656@indiana.edu>
<1211565622.17493.24.camel@jd-laptop>
<3C9DB43B-9B3D-4E55-B4DE-37E83A1CA136@indiana.edu>
<1211567980.17493.36.camel@jd-laptop>
<DC21DF01-8565-41A9-BD41-0B4B8535A259@indiana.edu>
<4836CDEA.EE98.0025.0@wicourts.gov>
<7B88EF79-78A5-4476-8A54-7EA42042A727@indiana.edu>
<483733F5.6020703@frostconsultingllc.com>
<4FAAB56B-864B-4B20-858A-4D5D0EA9E12E@indiana.edu>
Carol Walter wrote:
> -bash-3.00$ ps -ef | grep post
> postgres 9631 9629 0 Sep 24 ? 30:28
> /opt/csw/postgresql/bin/sparcv8/postgres -D /dbpdisk/postgres/prod_823
> postgres 9633 9629 0 Sep 24 ? 96:31
> /opt/csw/postgresql/bin/sparcv8/postgres -D /dbpdisk/postgres/prod_823
> postgres 9634 9629 0 Sep 24 ? 67:28
> /opt/csw/postgresql/bin/sparcv8/postgres -D /dbpdisk/postgres/prod_823
> postgres 9629 9396 0 Sep 24 ? 13:26
> /opt/csw/postgresql/bin/sparcv8/postgres -D /dbpdisk/postgres/prod_823
> postgres 12082 12029 0 17:57:06 pts/17 0:00 ps -ef
> postgres 12029 3950 0 17:55:05 pts/17 0:00 -bash
> postgres 12083 12029 0 17:57:06 pts/17 0:00 grep post
>
> I running under Solaris 10. I don't have anything that looks exactly
> like what you here, but the postgres has got to be running. I can go
> in as the postgres user connect to different databases and select data
> from them. This installation was loaded by my colleague using a
> product called Blastwave hence the csw directories.
>
> By the way, and not incidentally, thank you for the help.
Looks like pid 9629 is the parent of all of them, so if you simply:
kill 9629
they should all exit gracefully. You can check this with the same ps
command.
Then you should be able to: "pg_ctl -D /dbpdisk/postgres/prod_823 start"
as the postgres user to start it back up.
I think you might want to have a look at the /etc/init.d/postgresql (or
whatever the startup script is) because it doesn't look to be using
pg_ctl to start postgresql since the pid file was missing or ask your
colleague how it was started in the first place. I'm not sure on
Solaris if the ps output gets changed like it does in linux to reflect
the processes role. In linux those would probably look more like this:
postgres 2525 1 0 May02 ? 00:01:04 /usr/bin/postmaster -p
5432 -D /var/lib/pgsql/data
postgres 2649 2525 0 May02 ? 00:00:21 postgres: logger process
postgres 2662 2525 0 May02 ? 00:03:18 postgres: writer process
postgres 2663 2525 0 May02 ? 00:02:12 postgres: wal writer process
postgres 2664 2525 0 May02 ? 00:07:16 postgres: autovacuum
launcher process
postgres 2665 2525 0 May02 ? 00:04:56 postgres: stats
collector process
--
Jeff Frost, Owner <jeff@frostconsultingllc.com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jeff@frostconsultingllc.com, walterc@indiana.edu, Kevin.Grittner@wicourts.gov, jd@commandprompt.com
Subject: Re: Continuing issues... Can't vacuum!
In-Reply-To: <483742C9.6000906@frostconsultingllc.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox