| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, alvherre(at)2ndquadrant(dot)com, sbai(at)pivotal(dot)io, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Add tablespace tap test to pg_rewind |
| Date: | 2019-05-09 05:51:59 |
| Message-ID: | 20190509055159.GF14573@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 07, 2019 at 10:31:59AM +0900, Kyotaro HORIGUCHI wrote:
> The patch seems to be using the tablespace directory in backups
> directly from standbys. In other words, multiple standbys created
> from A backup shares the tablespace directory in the backup.
Yes, I noticed that, and I am not happy about that either. I'd like
to think that what we are looking for is an equivalent of the
tablespace mapping of pg_basebackup, but for init_from_backup(). At
least that sounds like a plausible solution.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2019-05-09 05:54:14 | Re: Unexpected "shared memory block is still in use" |
| Previous Message | Alex | 2019-05-09 05:48:49 | Re: any suggestions to detect memory corruption |