From: | Søren Laursen <sl(at)scrooge(dot)dk> |
---|---|
To: | |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Undo Update |
Date: | 2023-08-10 09:20:59 |
Message-ID: | CAOt+go8ncb8U0_3aU-ate+BQ82mEL2ZUD=eq4W6dsdcCNmqU_A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
https://www.postgresql.org/docs/current/backup.html
Best regards
Den tors. 10. aug. 2023 kl. 11.18 skrev Rajesh Kumar <
rajeshkumar(dot)dba09(at)gmail(dot)com>:
> 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?
>>>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar | 2023-08-10 09:52:37 | Re: Automate to rename table |
Previous Message | Rajesh Kumar | 2023-08-10 09:17:43 | Re: Undo Update |