Or use a SAVEPOINT. I don't know about the impact on resources if you
leave it hanging around for a long time, but I use these for exactly
the scenario you are talking about.
- Ian
On 4/16/07, Martin Langhoff <[EMAIL PROTECTED]> wrote:
On 4/17/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> Seems ov
On 4/17/07, Tom Lane <[EMAIL PROTECTED]> wrote:
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.
Thanks for the tip!
cheers
martin
---(end of broadcast)
Martin Langhoff wrote:
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
"Martin Langhoff" <[EMAIL PROTECTED]> 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
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 prist
