From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Martin Langhoff" <martin(dot)langhoff(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PITR - "Rewind to snapshot" scheme |
Date: | 2007-04-16 18:28:57 |
Message-ID: | 9007.1176748137@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Martin Langhoff" <martin(dot)langhoff(at)gmail(dot)com> writes:
> I have been following and experimenting a bit with PITR for a while,
> and I wonder whether it is practical to use the PITR hooks to roll
> back the database to a known state. The scenario is that I am
> developing a script that will be massaging data in a medium size
> database. A pg_restore of the pristine data takes ~35 minutes to
> complete, if I can take a snapshot right after pg_restore, and use it
> to later "rewind" to that point, I'll save 35 minutes every time I
> need to test it.
Seems overly complicated --- why don't you just shut down the postmaster
and take a tarball archive of the PGDATA tree? Then to revert, stop
postmaster and untar.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-04-16 18:33:02 | Re: pg_dump seg fault on sequences |
Previous Message | Alvaro Herrera | 2007-04-16 18:20:22 | Re: one more performance question I cannot test yet :( |