|From:||Fujii Masao <masao(dot)fujii(at)gmail(dot)com>|
|To:||Michael Banck <michael(dot)banck(at)credativ(dot)de>|
|Cc:||PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: [patch] reorder tablespaces in basebackup tar stream for backup_label|
|Views:||Raw Message | Whole Thread | Download mbox|
On Tue, Feb 21, 2017 at 7:17 PM, Michael Banck
> currently, the backup_label and (I think) the tablespace_map files are
> (by design) conveniently located at the beginning of the main tablespace
> tarball when making a basebackup. However, (by accident or also by
> design?) the main tablespace is the last tarball to be streamed via
> the BASE_BACKUP replication protocol command.
> For pg_basebackup, this is not a real problem, as either each tablespace
> is its own tarfile (in tar format mode), or the files are extracted
> anyway (in plain mode).
> However, third party tools using the BASE_BACKUP command might want to
> extract the backup_label, e.g. in order to figure out the START WAL
The first result set that BASE BACKUP sends back to a client contains
the START WAL LOCATION. So at first, ISTM that you don't need backup_label
for that purpose.
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
at the beginning even when WAL files are included in the backup.
|Next Message||Pavel Stehule||2017-03-28 19:10:23||Re: PoC plpgsql - possibility to force custom or generic plan|
|Previous Message||Tom Lane||2017-03-28 18:54:02||Re: Protection lost in expression eval changeover|