Re: Re: Backups WAS: 2 gig file size limit - Mailing list pgsql-general

From Doug McNaught
Subject Re: Re: Backups WAS: 2 gig file size limit
Date
Msg-id m3ith14ndo.fsf@belphigor.mcnaught.org
Whole thread Raw
In response to Re: [HACKERS] 2 gig file size limit  (Lamar Owen <lamar.owen@wgcr.org>)
List pgsql-general
[HACKERS removed from CC: list]

Joseph Shraibman <jks@selectacast.net> writes:


> Doing a dumpall for a backup is taking a long time, the a restore from
> the dump files doesn't leave the database in its original state.  Could
> a command be added that locks all the files, quickly tars them up, then
> releases the lock?

As I understand it, pg_dump runs inside a transaction, so the output
reflects a consistent snapshot of the database as of the time the dump
starts (thanks to MVCC); restoring will put the database back to where
it was at the start of the dump.

Have you observed otherwise?

-Doug
--
The rain man gave me two cures; he said jump right in,
The first was Texas medicine--the second was just railroad gin,
And like a fool I mixed them, and it strangled up my mind,
Now people just get uglier, and I got no sense of time...          --Dylan

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Partial indicies again
Next
From: Joseph Shraibman
Date:
Subject: Re: Re: Backups WAS: 2 gig file size limit