Re: [HACKERS] Contents of "backup_label" and "*.backup" in pg_wal location

2016-11-04 Thread Venkata B Nagothi
> On Fri, Nov 4, 2016 at 7:04 PM, Venkata B Nagothi > wrote: > > Sure. I will look at the possibility of using XLOG_BACKUP_END in my > patch. > > I am looking at the possibility of keeping the backup_label at source > until > > pg_stop_backup() > > is executed and then write the STOP information a

Re: [HACKERS] Contents of "backup_label" and "*.backup" in pg_wal location

2016-11-04 Thread Michael Paquier
On Fri, Nov 4, 2016 at 7:04 PM, Venkata B Nagothi wrote: > Sure. I will look at the possibility of using XLOG_BACKUP_END in my patch. > I am looking at the possibility of keeping the backup_label at source until > pg_stop_backup() > is executed and then write the STOP information and then move it

Re: [HACKERS] Contents of "backup_label" and "*.backup" in pg_wal location

2016-11-04 Thread Venkata B Nagothi
On Fri, Nov 4, 2016 at 3:44 PM, Michael Paquier wrote: > On Fri, Nov 4, 2016 at 1:18 PM, Venkata B Nagothi > wrote: > > I see the following contents in the file > > "00010044.0060.backup" which was generated in the > pg_wal > > location during the online backup. When pg_stop_

Re: [HACKERS] Contents of "backup_label" and "*.backup" in pg_wal location

2016-11-03 Thread Michael Paquier
On Fri, Nov 4, 2016 at 1:18 PM, Venkata B Nagothi wrote: > I see the following contents in the file > "00010044.0060.backup" which was generated in the pg_wal > location during the online backup. When pg_stop_backup() is executed, the > following content is written which includ