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 21:15:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
Carol Walter wrote:
> Hi, Again.
> I tried this and got the same message.  It is as follows:
> -bash-3.00$ /opt/csw/postgresql/bin/pg_ctl -D 
> /dbpdisk/postgres/prod_823 -m fas
> t stop
> pg_ctl: PID file "/dbpdisk/postgres/prod_823/" does not 
> exist
> Is server running?
> Are there other ideas?

Carol, what does:

ps -ef | grep postgres


If postgres is really running, there should be a postmaster process that 
shows which directory it's using as the DATA directory.  It'll look 
something like this:

postgres 24080     1  0 09:49 ?        00:00:07 /usr/bin/postmaster -p 
5432 -D /var/lib/pgsql/data

If there isn't a postmaster, it's possible someone started postgres with 
the -D option directly.

If you have multiple postgres server's running on the same machine, 
you'll see multiple postmasters.

BTW: What operating system is this running under?  If linux, which 

In response to


pgsql-admin by date

Next:From: Vishal MailinglistDate: 2008-05-23 21:34:30
Subject: Re: Error while executing pg_dump "invalid memory alloc request size 4294967293"
Previous:From: Carol WalterDate: 2008-05-23 21:01:03
Subject: Re: Continuing issues... Can't vacuum!

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