Re: recreating point-in-time recovery when tables are in non-default tablespace

From: Johannes Truschnigg <johannes(at)truschnigg(dot)info>
To: Mark Steben <mark(dot)steben(at)drivedominion(dot)com>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: recreating point-in-time recovery when tables are in non-default tablespace
Date: 2017-11-15 09:32:16
Message-ID: 20171115093215.nmix4fnqiccdi6jp@vault.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Nov 14, 2017 at 02:54:06PM -0500, Mark Steben wrote:
> Good afternoon,
>
> I have in the past been successful in creating a hot standby environment as
> all my tables were in one cluster on one disk. The base backup (I used tar)
> easily copied all tables and then the tar extract easily restored them on
> our standby server. [...]

Why don't you use pg_basebackup instead? It will take care of the gory details
and also handles tablespaces and tablespace mapping for you.

--
with best regards:
- Johannes Truschnigg ( johannes(at)truschnigg(dot)info )

www: https://johannes.truschnigg.info/
phone: +43 650 2 133337
xmpp: johannes(at)truschnigg(dot)info

Please do not bother me with HTML-email or attachments. Thank you.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Laurenz Albe 2017-11-15 10:06:05 Re: Vacuum not removing dead tuples
Previous Message Laurenz Albe 2017-11-15 09:27:15 Re: recreating point-in-time recovery when tables are in non-default tablespace