Skip site navigation (1) Skip section navigation (2)

Re: Continuing issues... Can't vacuum!

From: Jeff Frost <jeff(at)frostconsultingllc(dot)com>
To: Carol Walter <walterc(at)indiana(dot)edu>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Continuing issues... Can't vacuum!
Date: 2008-05-23 22:18:49
Message-ID: 483742C9.6000906@frostconsultingllc.com (view raw or flat)
Thread:
Lists: pgsql-admin

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(at)frostconsultingllc(dot)com>
Frost Consulting, LLC 	http://www.frostconsultingllc.com/
Phone: 650-780-7908	FAX: 650-649-1954


In response to

pgsql-admin by date

Next:From: Shane AmblerDate: 2008-05-24 09:30:43
Subject: Re: pgpass.conf
Previous:From: Carol WalterDate: 2008-05-23 22:04:18
Subject: Re: Continuing issues... Can't vacuum!

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group