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

Поиск
Список
Период
Сортировка
От Carol Walter
Тема Re: Continuing issues... Can't vacuum!
Дата
Msg-id 7B88EF79-78A5-4476-8A54-7EA42042A727@indiana.edu
обсуждение исходный текст
Ответ на Re: Continuing issues... Can't vacuum!  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Ответы Re: Continuing issues... Can't vacuum!  (Jeff Frost <jeff@frostconsultingllc.com>)
Список 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/postmaster.pid" does not
exist
Is server running?

Are there other ideas?

Carol

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

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


В списке pgsql-admin по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: 1600 column limit per table
Следующее
От: Jeff Frost
Дата:
Сообщение: Re: Continuing issues... Can't vacuum!