From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Any reason to use pg_dumpall on an idle database |
Date: | 2000-05-26 00:49:18 |
Message-ID: | 200005260049.UAA17322@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Thu, 25 May 2000, Bruce Momjian wrote:
>
> > > > 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?
> >
> > No, like everyone has gone home and nothing is happening.
>
> okay, so this is used on an IntraNet where 'schedualed downtime' is an
> option ... then doing a shutdown, tar, and startup makes sense ...
Yes, I was just trying to make it clear to them how a more simple backup
can happen.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-05-26 01:00:07 | Re: \dS and \df <pattern> crashing psql |
Previous Message | Nishad PRAKASH | 2000-05-26 00:37:12 | Re: \dS and \df <pattern> crashing psql |