From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Mark Steben <mark.steben@drivedominion.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: recreating point-in-time recovery when tables are in non-default tablespace
Date: Wed, 15 Nov 2017 10:27:15 +0100
Message-ID: <1510738035.2424.13.camel@cybertec.at> (raw)
In-Reply-To: <CADyzmyxx0UAcksUqeGRapKn4WZDQaT6JPcE-qy8n-cE5-ZyYFg@mail.gmail.com>
References: <CADyzmyxx0UAcksUqeGRapKn4WZDQaT6JPcE-qy8n-cE5-ZyYFg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Mark Steben wrote:
> 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.
> Since the last time this process was invoked I moved about 14 of these tables to a non-default tablespace on another disk
> (to alleviate space issues) Now the base backup does NOT pick up these tables and I am getting errors on the restore side.
>
> Here is a copy the error:
>
> : WARNING: page 36107 of relation pg_tblspc/1057768125/PG_9.4_201409291/16469/2231796047 is uninitialized
> Nov 14 13:46:20 ardbc01dr postgres[58399]: [572-2] @: CONTEXT: xlog redo delete: index 1057768125/16469/2231796047; iblk 36107, heap 1663/16469/2202113342;
> Nov 14 13:46:20 ardbc01dr postgres[58399]: [573-1] @: PANIC: WAL contains references to invalid pages
> Nov 14 13:46:20 ardbc01dr postgres[58399]: [573-2] @: CONTEXT: xlog redo delete: index 1057768125/16469/2231796047; iblk 36107, heap 1663/16469/2202113342;
> Nov 14 13:46:21 ardbc01dr postgres[58398]: [3-1] @: LOG: startup process (PID 58399) was terminated by signal 6: Aborted
>
> Am I out of luck here? Do I need to somehow move these tables back to the original cluster? Or is there another way?
I'd guess that you forgot to run
SELECT pg_start_backup('your_label');
before you copied the file and
SELECT pg_start_backup();
afterwards.
That will cause the backup to be corrupt.
Yours,
Laurenz Albe
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, mark.steben@drivedominion.com
Subject: Re: recreating point-in-time recovery when tables are in non-default tablespace
In-Reply-To: <1510738035.2424.13.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox