On Wed, Mar 29, 2017 at 5:36 PM, Kyotaro HORIGUCHI <horiguchi.kyot...@lab.ntt.co.jp> wrote: > Hello, > > At Wed, 29 Mar 2017 09:23:42 +0200, Michael Banck <michael.ba...@credativ.de> > wrote in <1490772222.18436.14.ca...@credativ.de> >> Hi, >> >> Am Mittwoch, den 29.03.2017, 15:22 +0900 schrieb Michael Paquier: >> > On Wed, Mar 29, 2017 at 3:56 AM, Fujii Masao <masao.fu...@gmail.com> wrote: >> > > If your need other information except START WAL LOCATION at the >> > > beginning of >> > > base backup and they are very useful for many third-party softwares, >> > > you can add them into that first result set. If you do this, you can >> > > retrieve them >> > > at the beginning even when WAL files are included in the backup. >> > >> > You mean in the result tuple of pg_start_backup(), right? Why not. >> >> The replication protocol chapter says: "When the backup is started, the >> server will first send two ordinary result sets, followed by one or more >> CopyResponse results. The first ordinary result set contains the >> starting position of the backup, in a single row with two columns." >> >> However, I don't think it is very obvious to users (or at least it is >> not to me) how to get at this from psql, if you want to script it. If I
I don't think that using psql to run BASE_BACKUP command is good approach. Instead, IMO you basically should implement the client program which can handle BASE_BACKUP properly, or extend pg_basebackup so that you can do what you want to do. Regards, -- Fujii Masao -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
