Re: backup manifests - Mailing list pgsql-hackers

From tushar
Subject Re: backup manifests
Date
Msg-id 22efd17f-e647-2b23-c5d4-350a24e4625b@enterprisedb.com
Whole thread Raw
In response to Re: backup manifests  (tushar <tushar.ahuja@enterprisedb.com>)
Responses Re: backup manifests  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 3/12/20 8:16 PM, tushar wrote:
Seems like expected behavior to me. We could consider providing a more
descriptive error message, but there's now way for it to work.

Right , Error message need to be more user friendly .

One scenario which i feel - should error out  even if  -s option is specified.
create  base  backup directory ( ./pg_basebackup data1)
Connect to root user and take out  the permission from pg_hba.conf file ( chmod 004 pg_hba.conf)

run pg_validatebackup - [centos@tushar-ldap-docker bin]$ ./pg_validatebackup data1
pg_validatebackup: error: could not open file "pg_hba.conf": Permission denied

run pg_validatebackup  with switch -s [centos@tushar-ldap-docker bin]$ ./pg_validatebackup data1 -s
pg_validatebackup: backup successfully verified

here file is not accessible so i think - it should throw you an error ( the same above one) instead of   blindly skipping it. 

-- 
regards,tushar
EnterpriseDB  https://www.enterprisedb.com/
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager
Next
From: Justin Pryzby
Date:
Subject: Re: bitmaps and correlation