Re: Any reason to use pg_dumpall on an idle database - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: Any reason to use pg_dumpall on an idle database
Date
Msg-id Pine.BSF.4.21.0005252114570.80347-100000@thelab.hub.org
Whole thread Raw
In response to Re: Any reason to use pg_dumpall on an idle database  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Any reason to use pg_dumpall on an idle database  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Thu, 25 May 2000, Bruce Momjian wrote:

> > On Thu, 25 May 2000, Bruce Momjian wrote:
> > 
> > > > On Thu, 25 May 2000, Bruce Momjian wrote:
> > > > 
> > > > > Seems a typical file system backup is fine on an idle database, right?
> > > > 
> > > > how do you know its idle, and/or will remain so?
> > > 
> > > pg_ctl stop of modification of pg_hba.conf.
> > 
> > ack ... why would you want to? *raised eyebrow*
> 
> Well, I am not sure.  In the book, I say you can use a normal file
> system backup if the database is idle, or use pg_dumpall and backup the
> file it creates.  In fact, once you run pg_dumpall, there is no need to
> backup the /data directory except for the few configuration files like
> pg_hba.conf.  Does this make sense?

when you mean 'idle', do you mean 'read-only'?  else the files in
/data/base/* would be changing, no? 




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Any reason to use pg_dumpall on an idle database
Next
From: Bruce Momjian
Date:
Subject: Re: Any reason to use pg_dumpall on an idle database