Re: PITR on DROP DATABASE, deleting of the database directory despite the recovery_target_time set before.

Hello, Le mar. 19 nov. 2019 à 16:15, Nicolas Lutic a écrit : > > We are aware that this part is tricky and will have little effects on > normal operations, as best practices are to use xid_target or lsn_target. > > I'm working with Nicolas and we made some further testing. If we use xid target

Re: PITR on DROP DATABASE, deleting of the database directory despite the recovery_target_time set before.

On 11/19/19 1:40 AM, Craig Ringer wrote: > On Mon, 18 Nov 2019 at 18:48, Nicolas Lutic > wrote: > > Dear Hackers, > > After a drop database > > > with FORCE? No, we tested with PostgreSQL v 11 and we don't have this option. >   > > , he tried to

Re: PITR on DROP DATABASE, deleting of the database directory despite the recovery_target_time set before.

On Mon, 18 Nov 2019 at 18:48, Nicolas Lutic wrote: > Dear Hackers, > > After a drop database > with FORCE? > , he tried to recover the data on the last inserted transaction by using > the recovery_target_time. > The issue is the database is present in the system catalog but the > directory

PITR on DROP DATABASE, deleting of the database directory despite the recovery_target_time set before.

Dear Hackers, A customer reported a strange behaviour on a PITR restoration.  After a drop database, he tried to recover the data on the last inserted transaction by using the recovery_target_time. The issue is the database is present in the system catalog but the directory was still deleted.