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

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

From: Carol Walter <walterc(at)indiana(dot)edu>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: "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:01:03
Message-ID: (view raw or whole thread)
Lists: pgsql-admin
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  
Is server running?

Are there other ideas?


This is the same error I got with the
On May 23, 2008, at 2:58 PM, Kevin Grittner wrote:

>>>> Carol Walter <walterc(at)indiana(dot)edu> wrote:
>> On May 23, 2008, at 2:39 PM, Joshua D. Drake wrote:
>>> pg_ctl -D /path/to/data/dir -m fast stop
>> Does this do an orderly, safe stop?  Also do I then bring it back up
>> with the usual command?
> "Three different shutdown methods can be selected with the -m option:
> "Smart" mode waits for all the clients to disconnect. This is the
> default. "Fast" mode does not wait for clients to disconnect. All
> active transactions are rolled back and clients are forcibly
> disconnected, then the server is shut down. "Immediate" mode will
> abort all server processes without a clean shutdown. This will lead to
> a recovery run on restart."
> From the docs:
> -Kevin

In response to


pgsql-admin by date

Next:From: Jeff FrostDate: 2008-05-23 21:15:33
Subject: Re: Continuing issues... Can't vacuum!
Previous:From: Tom LaneDate: 2008-05-23 20:31:16
Subject: Re: 1600 column limit per table

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