Tom, thanks for the advice. I brought up a new instance yesterday, with the
intent of trying it, and discovered that Wal-e with the "blind-restore"
option would put everything in the pg_tblspc directory, instead of
symlinking it. For this use case, that worked great.
Nate
On Wed, Jul 20, 2016 at
Nate Dudenhoeffer writes:
> 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?
You would definitely
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 a
On Wed, Jul 20, 2016 at 10:59 AM, Nate Dudenhoeffer 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 deve
