Re: pgbasebackup is failing after truncate - Mailing list pgsql-general

From Michael Paquier
Subject Re: pgbasebackup is failing after truncate
Date
Msg-id CAB7nPqSAKLRSm6pczMoBUtQhQY1JZHnTgUMY2rEgqpX+6z5=mQ@mail.gmail.com
Whole thread Raw
In response to Re: pgbasebackup is failing after truncate  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: pgbasebackup is failing after truncate  ("Yelai, Ramkumar" <ramkumar.yelai@siemens.com>)
List pgsql-general
On Sat, Aug 13, 2016 at 12:41 AM, Jeff Janes <jeff.janes@gmail.com> wrote:
> On Wed, Aug 10, 2016 at 11:06 PM, Yelai, Ramkumar
> <ramkumar.yelai@siemens.com> wrote:
>> At present, I have some requirement to truncate the data base  to reclaim
>> disk space and at the same time I need to take basebackup.
>>
>> Seems, truncate is successfully reclaimed the space but pgbasebackup failed
>> and reported the below error.
>>
>> “could not stat file or directory ./base/16384/25600: Permission denied.
>
> Are you on MS Windows?  If so, sounds like a possible variant of BUG #14243

That's really the same issue... See here for more details:
https://www.postgresql.org/message-id/20160712083220.1426.58667@wrigleys.postgresql.org
If you have ideas about making a difference between a real permission
error and STATUS_PENDING_DELETE, that would be great.
--
Michael


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Looking for software to 'enqueue' connections
Next
From: James Sewell
Date:
Subject: Re: Critical failure of standby