Postgres Pro
Downloads
Home   >   mailing lists

Re: Re: Table update: restore or replace? - Mailing list pgsql-general

From Rich Shepard
Subject Re: Re: Table update: restore or replace?
Date
Msg-id alpine.LNX.2.20.1905141513000.30120@salmo.appl-ecosys.com
Whole thread Raw
In response to Re: Re: Table update: restore or replace?  ("Brad Nicholson" <bradn@ca.ibm.com>)
List pgsql-general
Tree view 
On Tue, 14 May 2019, Brad Nicholson wrote:

> Might I suggest you setup proper backups with continuous archiving
> instead? If you had those, you would be able to restore this database back
> to the point right before you issued the bad update statement.
>
> I'd highly recommend pgBackRest for the task.

Brad,

I'll certainly take a look at pgBackRest.

Thanks,

Rich

pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: Table update: restore or replace?
Next
From: Rich Shepard
Date:
Subject: Re: Table update: restore or replace?