From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Ray Stell <stellr(at)vt(dot)edu>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_basebackup with a twist? |
Date: | 2018-02-02 21:11:12 |
Message-ID: | dbb38452-4325-ce25-fd8b-a93aef75f0d2@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 2/2/18 14:40, Ray Stell wrote:
> I have a fairly busy primary that I put a symlink in to move pg_xlog
> over to another I/O subsystem. I was going to build a standby with
> pg_basebackup running the command from the standby host. I thought
> maybe I could put the symlink in on the new standby, but no go:
> "pg_basebackup: directory "/database/test.basebackup/" exists but is not
> empty" as documented. Is the only way to do this to "fix" it up after
> the restore? I want to use the "-x" option in order to get the WAL
> during the backup. Just curious, my guess is I'll have to build the
> stby from a intermediate file. TIA.
pg_basebackup has a --waldir or --xlogdir (depending on version) option
for this, analogous to initdb.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-02-02 23:52:36 | Re: Extreme slowdown querying system tables |
Previous Message | Ray Stell | 2018-02-02 19:40:20 | pg_basebackup with a twist? |