From: | gleeco <gleeco(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | pg_basebackup restore & odd WAL |
Date: | 2016-05-27 06:21:44 |
Message-ID: | CADv14s_6fZT8XpjT=NYrRKm1-J2kTdGHSkremxMEVaV1SFV7cA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
hello - On 9.3, doing a restore of a sizeable db via pg_basebackup that was
taken from a slave.
the new db fails to start up b/c its recovery is looking for a WAL sequence
that does not exist (via the `backup_label` file?)
0000000700002949000000AF.lzo WANTED file
000000070000293A000000FE.lzo current - actual LIVE latest on master (24h
later even!)
Since it was non-critical, i toy'd around with it a bit, and even
`pg_resetxlog -f` did nothing.
how did my new restore get a sequence that looks far ahead (askew?) of the
current master which the backup was derived from? Any tl;dr solutions?
stumped
-gleeco
(and thanks in advance!)
From | Date | Subject | |
---|---|---|---|
Next Message | Nagy László Zsolt | 2016-05-30 05:26:43 | Could not shut down DB |
Previous Message | Andrew Glen-Young | 2016-05-26 19:37:24 | Systemtap + Postgresql production readiness |