Re: Multiple clusters with same tablespace location - Mailing list pgsql-general

From Nate Dudenhoeffer
Subject Re: Multiple clusters with same tablespace location
Date
Msg-id CAMtF5HBJTM1caM12n3uSqo=uYv8Vv_Rp-eQ48P+n=2Va2cMhBA@mail.gmail.com
Whole thread Raw
In response to Re: Multiple clusters with same tablespace location  (Melvin Davidson <melvin6925@gmail.com>)
Responses Re: Multiple clusters with same tablespace location  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Thanks for the response Melvin. 

The issue is that both clusters are using a base_backup and wal restore from the same master database, so when they are restored, the tablespace will already exist. Is there a way to change the tablespace location during the recovery process? 

On Wed, Jul 20, 2016 at 10:34 AM, Melvin Davidson <melvin6925@gmail.com> wrote:


On Wed, Jul 20, 2016 at 10:59 AM, Nate Dudenhoeffer <ndudenhoeffer@gmail.com> wrote:
What happens if I have two postgresql clusters running on the same server each with a tablespace pointing at the same location?

I have a production server, where I intend to move some tables to a second tablespace. I have a development/qa server which has multiple clusters running, each with a restore from the production server.

Thanks in advance,
Nate

Pointing multiple clusters to the same tablespace is a very bad idea. You run the risk of overwriting a file with the same name from a different cluster.
Think of Ghostbusters ->"Don't cross the streams"!.
There is no reason why you cannot have separate directories for each cluster/tablespace, so why ask for trouble?

--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.


pgsql-general by date:

Previous
From: Melvin Davidson
Date:
Subject: Re: Multiple clusters with same tablespace location
Next
From: John DeSoi
Date:
Subject: Re: MediaWiki + PostgreSQL is not ready for production?