RE: Complete data erasure - Mailing list pgsql-hackers

From asaba.takanori@fujitsu.com
Subject RE: Complete data erasure
Date
Msg-id OSBPR01MB4728EE99EB295624643409C98C130@OSBPR01MB4728.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Complete data erasure  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses RE: Complete data erasure  ("asaba.takanori@fujitsu.com" <asaba.takanori@fujitsu.com>)
List pgsql-hackers
Hello Tom,

From: Tom Lane <tgl@sss.pgh.pa.us>
> Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:
> > I think it depends how exactly it's implemented. As Tom pointed out in
> > his message [1], we can't do the erasure itself in the post-commit is
> > not being able to handle errors. But if the files are renamed durably,
> > and the erasure happens in a separate process, that could be OK. The
> > COMMIT may wayt for it or not, that's mostly irrelevant I think.
>
> How is requiring a file rename to be completed post-commit any less
> problematic than the other way?  You still have a non-negligible
> chance of failure.

I think that errors of rename(2) listed in [1] cannot occur or can be handled.
What do you think?

[1] http://man7.org/linux/man-pages/man2/rename.2.html


Regards,

--
Takanori Asaba





pgsql-hackers by date:

Previous
From: "asaba.takanori@fujitsu.com"
Date:
Subject: RE: Complete data erasure
Next
From: Amit Langote
Date:
Subject: Re: Autovacuum on partitioned table