search for: pg_start_backup

...last will ensure consistent state of everything in your > dump. I usually use combination: I do dbdump, and back up these dump files > on regular backup schedule (and exclude db files from backup). for postgresql, you can use rsync style copies of the file system if you bracket the rsync 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 comman...

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