Greetings, * julyanto SUTANDANG (julyanto@xxxxxxxxxxxx) wrote: > CORRECTION: > > "you might you pg_start_backup to tell the server not to write into the > DATADIR" > > become > > "you might *use* pg_start_backup to tell the server not to write into the > *BASEDIR*, actually server still writes but only to XLOGDIR " Just to make sure anyone reading the mailing list archives isn't confused, running pg_start_backup does *not* make PG stop writing to BASEDIR (or DATADIR, or anything, really). PG *will* continue to write data into BASEDIR after pg_start_backup has been called. The only thing that pg_start_backup does is identify an entry in the WAL stream, from which point all WAL must be replayed when restoring the backup. All WAL generated from that point (pg_start_backup point) until the pg_stop_backup point *must* be replayed when restoring the backup or the database will not be consistent. Thanks! Stephen
Attachment:
signature.asc
Description: Digital signature
