Re: Continuing issues... Can't vacuum! - Mailing list pgsql-admin

From Jeff Frost
Subject Re: Continuing issues... Can't vacuum!
Date
Msg-id 483733F5.6020703@frostconsultingllc.com
Whole thread Raw
In response to Re: Continuing issues... Can't vacuum!  (Carol Walter <walterc@indiana.edu>)
Responses Re: Continuing issues... Can't vacuum!
List 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/postmaster.pid" does not
> exist
> Is server running?
>
> Are there other ideas?

Carol, what does:

ps -ef | grep postgres

return?

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
distribution?



pgsql-admin by date:

Previous
From: Carol Walter
Date:
Subject: Re: Continuing issues... Can't vacuum!
Next
From: "Vishal Mailinglist"
Date:
Subject: Re: Error while executing pg_dump "invalid memory alloc request size 4294967293"