Обсуждение: BUG #14321: pg_basebackup --xlog-method=stream fails
VGhlIGZvbGxvd2luZyBidWcgaGFzIGJlZW4gbG9nZ2VkIG9uIHRoZSB3ZWJz aXRlOgoKQnVnIHJlZmVyZW5jZTogICAgICAxNDMyMQpMb2dnZWQgYnk6ICAg ICAgICAgIErDvHJnZW4gU3Ryb2JlbApFbWFpbCBhZGRyZXNzOiAgICAgIGp1 ZXJnZW4rcG9zdGdyZXNxbEBzdHJvYmVsLmluZm8KUG9zdGdyZVNRTCB2ZXJz aW9uOiA5LjUuNApPcGVyYXRpbmcgc3lzdGVtOiAgIENlbnRPUzcKRGVzY3Jp cHRpb246ICAgICAgICAKCkhlbGxvIGV2ZXJ5b25lLA0KDQpRdWl0ZSBvZnRl biB3aGlsZSBydW5uaW5nIHBnX2Jhc2ViYWNrdXAgLS14bG9nLW1ldGhvZD1z dHJlYW0gSSBnZXQgdGhlCmZvbGxvd2luZyB3YXJuaW5nOg0KDQpwZ19iYXNl YmFja3VwOiBjb3VsZCBub3QgcmVjZWl2ZSBkYXRhIGZyb20gV0FMIHN0cmVh bTogc2VydmVyIGNsb3NlZCB0aGUKY29ubmVjdGlvbiB1bmV4cGVjdGVkbHkN CiAgICAgICAgVGhpcyBwcm9iYWJseSBtZWFucyB0aGUgc2VydmVyIHRlcm1p bmF0ZWQgYWJub3JtYWxseQ0KICAgICAgICBiZWZvcmUgb3Igd2hpbGUgcHJv Y2Vzc2luZyB0aGUgcmVxdWVzdC4NCg0KVGhlIGZpbHN5c3RlbSBiYWNrdXAg Y29udGludWVzIHN1Y2Nlc3NmdWxseSB0byBpdHMgZW5kLCBidXQgaXQgY29u Y2x1ZGVzCndpdGhvdXQgdGhlIG5lY2Vzc2FyeSBXQUwgZmlsZXMuIEkgdmVy aWZpZWQgaW4gcGdfc3RhdF9yZXBsaWNhdGlvbiB0aGF0CnBnX2Jhc2ViYWNr dXAgaXMgbm90IHRyeWluZyB0byByZWNvbm5lY3QgdG8gdGhlIG1hc3Rlci4N Cg0KSSBhbSBydW5uaW5nIHRoaXMgaW4gYSBWTSB0YWtpbmcgYSBiYWNrdXAg b2YgYSBsaXZlIH4zMDAtOTAwR0IgREJzLgpTb21ldGltZXMgSU8gc3Bpa2Vz IHNlZW0gdG8gY2F1c2UgaGFuZ3MgbGFyZ2VyIHRoYW4gdGhlIHNlcnZlcidz CndhbF9zZW5kZXJfdGltZW91dCwgd2hpY2ggaXMgdGhlIGRlZmF1bHQgNjBz LiBUaGUgVk0gaGFzIG11Y2ggbGVzcyByZXNvdXJjZXMKdGhhbiB0aGUgdXBz dHJlYW0gREIuIEkgZG9uJ3QgcmVhbGx5IHdhbnQgdG8gaW5jcmVhc2Ugd2Fs X3NlbmRlcl90aW1lb3V0CmJlY2F1c2UgdGhlcmUgYXJlIG90aGVyIChub24t YmFja3VwKSBIQSBzdGFuZGJ5cyB0b28sIGFuZCBJIHdvdWxkbid0IGtub3cg dG8KaG93IG11Y2guDQoNCkkgdW5kZXJzdGFuZCBob3cgdG8gcmVwYWlyIHRo aXMgbWFudWFsbHkgYW5kIGl0J3Mgbm90IGFuIGVuZC1vZi10aGUtd29ybGQK YnVnLCBidXQgaXQgd291bGQgYmUgbmljZSBpZiBwZ19iYXNlYmFja3VwIHdv dWxkIGp1c3QgcmVjb25uZWN0IHRoZQpzdHJlYW1pbmcgV0FMIGNvbm5lY3Rp b24gaW4gdGhlIHNhbWUgd2F5IGFzIHBnX3JlY2VpdmV4bG9nIGRvZXMuIEVz cGVjaWFsbHkKYXMgdGhhdCBlcnJvciBoYXBwZW5zIGluIGEgbG9uZyBzY3Jp cHQgcnVuIGJ5IGNyb24gYW5kL29yIG90aGVyIHBlb3BsZSB3aG8KZG8gbm90 IGhhdmUgdGhpcyBpbnNpZ2h0Lg0KDQpJIGhhdmVuJ3QgaGFkIHRpbWUgdG8g dHJ5IDkuNidzIC0tc2xvdCBvcHRpb24geWV0LCBidXQgSSBzdXNwZWN0IHRo aXMgd29uJ3QKYmUgYSBmdWxsIGN1cmUgZWl0aGVyIHVubGVzcyBpdCBhbHNv IGNoYW5nZXMgdGhlIHJlLWNvbm5lY3QgYmVoYXZpb3IuDQoNCkJlc3QgcmVn YXJkcywNCkrDvHJnZW4gU3Ryb2JlbA0KDQoNCg0KDQoKCg==
On Sat, Sep 10, 2016 at 1:58 AM, <juergen+postgresql@strobel.info> wrote: > The filsystem backup continues successfully to its end, but it concludes > without the necessary WAL files. I verified in pg_stat_replication that > pg_basebackup is not trying to reconnect to the master. > > I understand how to repair this manually and it's not an end-of-the-world > bug, but it would be nice if pg_basebackup would just reconnect the > streaming WAL connection in the same way as pg_receivexlog does. Especially > as that error happens in a long script run by cron and/or other people who > do not have this insight. Perhaps. The source server logs do prove the fact that pg_basebackup is requesting for missing WAL segments, right? > I haven't had time to try 9.6's --slot option yet, but I suspect this won't > be a full cure either unless it also changes the re-connect behavior. If what you are seeing missing are the first WAL segments that your backup needs, first the backup you took will be useless if you don't have a WAL archive from where recovery could fetch those missing segments. And in this case --slot will definitely help, but just be sure that this does not bloat your pg_xlog partition if disk space is a concern there. -- Michael