Gregory Stark wrote:
"Kris Jurka" <[EMAIL PROTECTED]> writes:

On Mon, 28 Jan 2008, Jeff Davis wrote:

I think that pg_dump is a reasonable use case for synchoronized scans
when the table has not been clustered. It could potentially make pg_dump
have much less of a performance impact when run against an active
One of the advantages I see with maintaining table dump order is that rsyncing
backups to remote locations will work better.

I can't see what scenario you're talking about here. pg_dump your live
database, restore it elsewhere, then shut down the production database and run
rsync from the live database to the restored one? Why not just run rsync for
the initial transfer?

take a dump (maybe in plaintext format) save it to disk and use rsync to copy it elsewhere. the more "similiar" the dumps the more efficient rsync can copy the data over.


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?


Reply via email to