pgbasebackup is failing after truncate - Mailing list pgsql-general

From Yelai, Ramkumar
Subject pgbasebackup is failing after truncate
Date
Msg-id FFF1B7B19FDD154B8933AFF9E40855B20FE3E93E2D@INBLRK77M2MSX.in002.siemens.net
Whole thread Raw
Responses Re: pgbasebackup is failing after truncate  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: pgbasebackup is failing after truncate  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-general
HI
 
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.
 
Further observation shows that truncate command reclaiming the space by making empty (not deleted)  these files in ./base/16384 folders.
 
Seems these filename are relfilenode in pg_class table to map filename to table name. Since truncate making empty these files and create new files to map the old table name, pgbasebackup is unable to synch with truncate and pointing to old files.
 
Also, the old files are not deleted from “base” folder.
 
Please let me know how to resolve this issue
 
With best regards,
Ramkumar Yelai
 
 
Registered Office: 130, Pandurang Budhkar Marg, Worli, Mumbai 400 018. Telephone +91 22 39677000. Fax +91 22 39677075. Other Offices: Bangalore, Chennai, Gurgaon, Noida, Kolkata, Pune. Corporate Identity number:U99999MH1986PLC093854
 
 

pgsql-general by date:

Previous
From: Chris Travers
Date:
Subject: Re: Postgres Pain Points 2 ruby / node language drivers
Next
From: "hari.prasath"
Date:
Subject: Re: Jsonb extraction very slow