search for: pg_basebackup

...c in pg_start_backup(); and pg_stop_backup() calls. dumps (pg_dump) are fine for smaller databases, but become really unwieldy for very large ones, and a straight database file system copy like rsync is required to initialize a streaming replication slave (although this can be done with the pg_basebackup command line util, there's times when doing it manually is appropriate). filesystem level snapshots such as provided by ZFS are also very workable for such databases, as they are point-in-time views of the filesystem. even if transactions are in process when the snapshot is made, if its l...

I'm trying to streamline a backup system using ZFS. In our situation, we're writing pg_dump files repeatedly, each file being highly similar to the previous file. Is there a file system (EG: ext4? xfs?) that, when re-writing a similar file, will write only the changed blocks and not rewrite the entire file to a new set of blocks? Assume that we're writing a 500 MB file with only

On Thu, June 9, 2016 1:14 pm, John R Pierce wrote: > where Rsync falls down, is if you need a point in time snapshot... Rsync > processes one file at a time, so if the files are being updated while > its running, the differnet files will be copied at different times. > This is usually fine for static archives of files and such, but > unsuitable for a database server where random