Re: backup manifests and contemporaneous buildfarm failures - Mailing list pgsql-hackers

From Tom Lane
Subject Re: backup manifests and contemporaneous buildfarm failures
Date
Msg-id 4026.1586117546@sss.pgh.pa.us
Whole thread Raw
In response to Re: backup manifests and contemporaneous buildfarm failures  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: backup manifests and contemporaneous buildfarm failures  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> Hmm, the buildfarm client does this at the beginning of each run to
> remove anything that might be left over from a previous run:

>     rmtree("inst");
>     rmtree("$pgsql") unless ($from_source && !$use_vpath);

Right, the point is precisely that some versions of rmtree() fail
to remove a mode-0 subdirectory.

> Do I need to precede those with some recursive chmod commands? Perhaps
> the client should refuse to run if there is still something left after
> these.

I think the latter would be a very good idea, just so that this sort of
failure is less obscure.  Not sure about whether a recursive chmod is
really going to be worth the cycles.  (On the other hand, the normal
case should be that there's nothing there anyway, so maybe it's not
going to be costly.)  

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: backup manifests and contemporaneous buildfarm failures
Next
From: Justin Pryzby
Date:
Subject: Re: VACUUM memory management