Re: pg_dump in stand alone backend - Mailing list pgsql-general

From Gaetano Mendola
Subject Re: pg_dump in stand alone backend
Date
Msg-id 4129FE05.5020402@bigfoot.com
Whole thread Raw
In response to pg_dump in stand alone backend  (Ulrich Wisser <ulrich.wisser@relevanttraffic.se>)
Responses Re: pg_dump in stand alone backend  (Ulrich Wisser <ulrich.wisser@relevanttraffic.se>)
List pgsql-general
Ulrich Wisser wrote:

> Hi,
>
> I would like to stop the postmaster every night and run
>
> vacuum
> pg_dump
> reindex
>
> in the stand alone backend.
>
> Vacuum and reindex seem to be quite easy, as I can setup a small script
> with both commands. But what about pg_dump. That seems "somewhat" more
> complex.

Explain what exactly you are trying to do, why do you have to stop
the postmaster ? If you request is due only to forbid the access then
you can replace the pg_hba.conf with a "void" one and replace it again
at the end of operations.

BTW vacuum, pg_dump, reindex are operations that can be performed
with the server up and running.

Regards
Gaetano Mendola




pgsql-general by date:

Previous
From: Gaetano Mendola
Date:
Subject: Re: Connection to a PG 8.0 Beta 1 win32 server
Next
From: "Marc G. Fournier"
Date:
Subject: Re: Unsupported 3rd-party solutions (Was: Few questions