From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Marc Millas <marc(dot)millas(at)mokadb(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Extract transactions from wals ?? |
Date: | 2019-11-21 14:54:16 |
Message-ID: | 355aa1f83ee7bf0b2f5296f46cf231fb1384b409.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 2019-11-21 at 14:50 +0100, Marc Millas wrote:
> due to a set of bugs and wrong manip, an inappropriate update have been done into a production DB.
> After that, quite a long set of valuables inserts and updates have been done and needs to be kept.
> Obviously getting a backup and applying pitr will get us just before the offending update.
> Now, we need to find a way of extracting, either from the ex prod db, or from the wals, the "good" transactions to be able to re-apply them.
>
> This did already happen on a Prod Oracle DB, and recovering was possible with a :
> select * from table_name AS OF TIMESTAMP TO_TIMESTAMP('09052019 0900','MMDDYYYY HH24MI');
> to get most things done after the problem.
> As we are currently moving out of Oracle, we must prove to the business people that our new postgres env is fine.
> So, ... any idea ?
Sure.
Restore a backup and perform point-in-time-recovery.
Then extract the data you need.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2019-11-21 14:54:54 | Re: Tablespace setup issue |
Previous Message | Ron | 2019-11-21 14:53:27 | Re: Isolation of multiple databse instances provided by a single postgres server |