Re: [ADMIN] recreating point-in-time recovery when tables are innon-default tablespace - Mailing list pgsql-admin

From Mark Steben
Subject Re: [ADMIN] recreating point-in-time recovery when tables are innon-default tablespace
Date
Msg-id CADyzmyw-M4v-GXfaFc9dStgeH_rkvMQQ6-fmDtftd5ZFxDAZJA@mail.gmail.com
Whole thread Raw
In response to Re: [ADMIN] recreating point-in-time recovery when tables are innon-default tablespace  (Johannes Truschnigg <johannes@truschnigg.info>)
List pgsql-admin
Thank you gentlemen, for your prompt response.
Laurenz, I have pg_start_backup and pg_stop_backup included in my base backup shell script.  They ran.

Johannes, I will attempt using pg_basebackup.  It looks like the tablespace-mapping option would help here.

Thanks again
  

On Wed, Nov 15, 2017 at 4:32 AM, Johannes Truschnigg <johannes@truschnigg.info> wrote:
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@truschnigg.info )

www:   https://johannes.truschnigg.info/
phone: +43 650 2 133337
xmpp:  johannes@truschnigg.info

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



--
Mark Steben
 Database Administrator
@utoRevenue | Autobase 
  CRM division of Dominion Dealer Solutions 
95D Ashley Ave.
West Springfield, MA 01089

t: 413.327-3045
f: 413.383-9567

www.fb.com/DominionDealerSolutions
www.twitter.com/DominionDealer
 www.drivedominion.com





pgsql-admin by date:

Previous
From: Debraj Manna
Date:
Subject: Re: [ADMIN] Upgrade 9.5 cluster with non default data directory with checksum
Next
From: sighup
Date:
Subject: [ADMIN] Issue with pg_ident after password change on v10.0