From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Undo Update |
Date: | 2023-08-10 15:08:51 |
Message-ID: | a8a65ba3-de54-d937-488d-07ccddba6eb0@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ask your database administrator about PITR (Point In Time Recovery).
On 8/10/23 04:17, Rajesh Kumar wrote:
> In that case, how to take a backup specifically before that update and are
> there any prequisites such as stopping the server when it happens? And
> then backup like that?
>
> On Thu, 10 Aug, 2023, 2:36 PM Holger Jakobs, <holger(at)jakobs(dot)com> wrote:
>
> I'm afraid you will have to execute the SQL statement undoing it. Of
> you don't know the previous values, you're out of luck.
>
> Then a backup is your best friend.
>
>
> Am 10. August 2023 11:02:26 MESZ schrieb Rajesh Kumar
> <rajeshkumar(dot)dba09(at)gmail(dot)com>:
>
> Hi friends
>
> I was given a query to update the record in table A with where
> clause. But I executed it in production mistakenly without where
> clause so it updated incorrectly for all rows.
>
> How do I resolve this?
>
--
Born in Arizona, moved to Babylonia.
From | Date | Subject | |
---|---|---|---|
Next Message | Wetmore, Matthew (CTR) | 2023-08-10 15:27:24 | Automate to rename table |
Previous Message | Ron | 2023-08-10 15:07:19 | Re: Automate to rename table |