From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Joshua D. Drake <jd@commandprompt.com>
To: Carol Walter <walterc@indiana.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: Continuing issues... Can't vacuum!
Date: Fri, 23 May 2008 13:58:42 -0500
Message-ID: <4836CDEA.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <DC21DF01-8565-41A9-BD41-0B4B8535A259@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>
>>> Carol Walter <walterc@indiana.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:
http://www.postgresql.org/docs/8.2/interactive/app-pg-ctl.html
-Kevin
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: Kevin.Grittner@wicourts.gov, jd@commandprompt.com, walterc@indiana.edu
Subject: Re: Continuing issues... Can't vacuum!
In-Reply-To: <4836CDEA.EE98.0025.0@wicourts.gov>
* 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