Re: ERROR: could not open file "pg_tblspc/ issue with replication setup.

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>
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 04:21:02
Message-ID: 20200417041758.GJ81957@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-04-17 04:40:02 Re: It is not documented that pg_promote can exit standby mode
Previous Message ikedamsh 2020-04-17 04:11:31 It is not documented that pg_promote can exit standby mode