|Subject:||BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
The following bug has been logged on the website:
Bug reference: 14243
Logged by: TAKATSUKA Haruka
Email address: harukat(at)sraoss(dot)co(dot)jp
PostgreSQL version: 9.6beta2
Operating system: Windows
pg_basebackup sometimes failed on Windows by "Permission denied".
This occured in PostgreSQL 9.1.x and I reproduced it in 9.6beta2.
C:\>pg_basebackup.exe -h localhost -U postgres
-D C:\dat\96datpg_basebackup: could not get backup header:
ERROR: could not stat file or directory "./base/16393/16444":
C:\Program Files\PostgreSQL\9.6\data\base\16393>dir /q 16444
C:\Program Files\PostgreSQL\9.6\data\base\16393 directory
2016/07/12 15:56 0 ... 16444
Dir command says the file 16444's owner is '...'.
It means file 16444 is in STATUS_DELETE_PENDING.
The other processes cannot open it, so it can
cause pg_basebackup to fail.
I think pg_basebackup should ignore files which is in
STATUS_DELETE_PENDING. But I cannot yet find an easy
method to realize it.
|Next Message||Alvaro Herrera||2016-07-12 13:21:28||Re: Incorrect Spanish error message.|
|Previous Message||David G. Johnston||2016-07-12 02:15:38||Re: BUG #14242: Role with a setconfig "role" setting to a nonexistent role causes pg_upgrade to fail|