| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Curt Sampson <cjs(at)cynic(dot)net> |
| Cc: | Doug Fields <dfields-pg-general(at)pexicom(dot)com>, Darren Ferguson <darren(at)crystalballinc(dot)com>, Sanjeev Rathore <intmail2002(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: database backup |
| Date: | 2002-07-08 03:48:10 |
| Message-ID: | 200207080348.g683mAQ08299@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Curt Sampson wrote:
> On Sat, 6 Jul 2002, Doug Fields wrote:
>
> > >Then the shell script in the cron job can call pg_dump with the relevant
> > >options
> >
> > If you want to "incrementalize" it, you could always keep a base, and diff
> > the new dump against it, and store just the diff.
>
> Actually, I was wondering just yesterday, is there any reason that
> pg_dump should not be able to do an incremental dump? You could just
> give it a transaction ID and say, "dump all changes from this ID."
I think the problem is matching up rows in the old dump with the
incremental rows.
--
Bruce Momjian | http://candle.pha.pa.us
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 | Curt Sampson | 2002-07-08 03:54:57 | Re: Efficient use of space in large table? |
| Previous Message | Jillian Carroll | 2002-07-08 03:33:00 | Date Data Type |