From: | Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ERROR: could not open file "pg_tblspc/ issue with replication setup. |
Date: | 2020-04-17 06:39:51 |
Message-ID: | CAKcux6kEwNPv2WnoLhBpa_1UsR6gZqzQTqaacUN432YBvSK3+g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 17, 2020 at 9:51 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Thu, Apr 16, 2020 at 01:56:47PM +0530, Rajkumar Raghuwanshi wrote:
> > While testing for a feature I got this tablespace related error while
> > running script.
>
> Primary and standby are running on the same host, so they would
> interact with each other as the tablespace path used by both clusters
> would be the same (primary uses the path defined by the DDL, which is
> registered in the WAL record the standby replays). What you are
> looking for here is to create the tablespace before taking the base
> backup, and then use the option --tablespace-mapping with
> pg_basebackup to avoid the issue.
>
Thanks for the help.
> --
> Michael
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2020-04-17 06:50:43 | Re: [BUG] non archived WAL removed during production crash recovery |
Previous Message | Masahiko Sawada | 2020-04-17 06:18:51 | Re: xid wraparound danger due to INDEX_CLEANUP false |