Thread: BUG #14233: getting the size if the database failing with permission denied error
BUG #14233: getting the size if the database failing with permission denied error
From
ssatyasrinivas@gmail.com
Date:
VGhlIGZvbGxvd2luZyBidWcgaGFzIGJlZW4gbG9nZ2VkIG9uIHRoZSB3ZWJz aXRlOgoKQnVnIHJlZmVyZW5jZTogICAgICAxNDIzMwpMb2dnZWQgYnk6ICAg ICAgICAgIFNhdHlhIFN1bmthcmEKRW1haWwgYWRkcmVzczogICAgICBzc2F0 eWFzcmluaXZhc0BnbWFpbC5jb20KUG9zdGdyZVNRTCB2ZXJzaW9uOiA5LjIu OQpPcGVyYXRpbmcgc3lzdGVtOiAgIHdpbmRvd3MKRGVzY3JpcHRpb246ICAg ICAgICAKCndoZW4gd2UgZG8gdGhlIGJhY2t1cCwgd2UgZG8gcXVlcnkgdGhl IERCIGZvciBzaXplIGFuZCBuYW1lIHVzaW5nIGZvbGxvd2luZwpzZWxlY3Qg c3RhdGVtZW50Og0KDQpzZWxlY3QgcC5kYXRuYW1lLHBnX2RhdGFiYXNlX3Np emUocC5kYXRuYW1lKSBmcm9tIHBnX2RhdGFiYXNlIHANCg0KVGhpcyBxdWVy eSBpcyB0aHJvd3MgZXJyb3I6DQoNClBRcmVzdWx0U3RhdHVzIGluZGljYXRl cyBmYWlsdXJlIGZvciBzZWxlY3QKcC5kYXRuYW1lLHBnX2RhdGFiYXNlX3Np emUocC5kYXRuYW1lKSBmcm9tIHBnX2RhdGFiYXNlIHAuIEVycm9yOkVSUk9S OiAKY291bGQgbm90IHN0YXQgZmlsZSAiYmFzZS85NTgyMS8yNzI1NzQiOiBQ ZXJtaXNzaW9uIGRlbmllZA0KDQpJcyB0aGVyZSBhbnkgcmVzb2x1dGlvbiBm b3IgdGhpcz8NCg0KDQoNCg0KCgo=
Re: BUG #14233: getting the size if the database failing with permission denied error
From
Julien Rouhaud
Date:
On 07/07/2016 17:01, ssatyasrinivas@gmail.com wrote: > The following bug has been logged on the website: > > Bug reference: 14233 > Logged by: Satya Sunkara > Email address: ssatyasrinivas@gmail.com > PostgreSQL version: 9.2.9 > Operating system: windows > Description: > > when we do the backup, we do query the DB for size and name using following > select statement: > > select p.datname,pg_database_size(p.datname) from pg_database p > > This query is throws error: > > PQresultStatus indicates failure for select > p.datname,pg_database_size(p.datname) from pg_database p. Error:ERROR: > could not stat file "base/95821/272574": Permission denied > > Is there any resolution for this? > This is not a bug, such a question should be sent on a mailing list like pgsql-general. Your problem is that the system user running the cluster (probably "postgres") doesn't have access on this file anymore. You should investigate why and how file permission has been changed, and restore the regular permissions. -- Julien Rouhaud http://dalibo.com - http://dalibo.org