Re: Large Database Restore - Mailing list pgsql-general

From Ron Johnson
Subject Re: Large Database Restore
Date
Msg-id 464CBFB7.9080606@cox.net
Whole thread Raw
In response to Re: Large Database Restore  ("Jim C. Nasby" <decibel@decibel.org>)
Responses Re: Large Database Restore
List pgsql-general
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/17/07 11:04, Jim C. Nasby wrote:
[snip]
>
> Ultimately though, once your database gets past a certain size, you
> really want to be using PITR and not pg_dump as your main recovery
> strategy.

But doesn't that just replay each transaction?  It must manage the
index nodes during each update/delete/insert, and multiple UPDATE
statements means that you hit the same page over and over again.

- --
Ron Johnson, Jr.
Jefferson LA  USA

Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGTL+3S9HxQb37XmcRAqGyAKDYxtahXCuZD0WkNV8fY8p48Wcn2gCgk3hQ
ExVOZQBDuVVafTqB1XD/Gno=
=6Pzi
-----END PGP SIGNATURE-----

pgsql-general by date:

Previous
From: "Robert James"
Date:
Subject: Re: Postgres Printed Manuals
Next
From: Ron Johnson
Date:
Subject: Re: Fault Tolerant Postgresql (two machines, two postmasters, one disk array)