Re: Backup taking long time !!!

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: julyanto SUTANDANG <julyanto(at)equnix(dot)co(dot)id>
Cc: Dinesh Chandra 12108 <Dinesh(dot)Chandra(at)cyient(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Backup taking long time !!!
Date: 2017-01-22 14:57:40
Message-ID: 20170122145740.GE18360@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Greetings,

* julyanto SUTANDANG (julyanto(at)equnix(dot)co(dot)id) 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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message julyanto SUTANDANG 2017-01-22 16:04:13 Re: Backup taking long time !!!
Previous Message Stephen Frost 2017-01-22 14:55:11 Re: Backup taking long time !!!