From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | "Yelai, Ramkumar" <ramkumar(dot)yelai(at)siemens(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pgbasebackup is failing after truncate |
Date: | 2016-08-16 00:20:42 |
Message-ID: | CAB7nPqSAKLRSm6pczMoBUtQhQY1JZHnTgUMY2rEgqpX+6z5=mQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Aug 13, 2016 at 12:41 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Wed, Aug 10, 2016 at 11:06 PM, Yelai, Ramkumar
> <ramkumar(dot)yelai(at)siemens(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | James Sewell | 2016-08-16 02:23:11 | Re: Critical failure of standby |
Previous Message | Adrian Klaver | 2016-08-15 22:58:08 | Re: Looking for software to 'enqueue' connections |