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:23:12 |
Message-ID: | 200005260023.UAA15008@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > 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.
--
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 | The Hermit Hacker | 2000-05-26 00:35:10 | Re: Any reason to use pg_dumpall on an idle database |
Previous Message | The Hermit Hacker | 2000-05-26 00:15:27 | Re: Any reason to use pg_dumpall on an idle database |