Обсуждение: BUG #14312: Hardcoded dbname on test_postmaster_connection

VGhlIGZvbGxvd2luZyBidWcgaGFzIGJlZW4gbG9nZ2VkIG9uIHRoZSB3ZWJz
aXRlOgoKQnVnIHJlZmVyZW5jZTogICAgICAxNDMxMgpMb2dnZWQgYnk6ICAg
ICAgICAgIEhlcm5hbiBCYXphbgpFbWFpbCBhZGRyZXNzOiAgICAgIGhlcm5h
bi5iYXphbkBpbnRlbC5jb20KUG9zdGdyZVNRTCB2ZXJzaW9uOiA5LjMuMTQK
T3BlcmF0aW5nIHN5c3RlbTogICBNTE9TCkRlc2NyaXB0aW9uOiAgICAgICAg
CgpXaGVuIGNhbGxpbmcgInBnX2N0bCBzdGFydCIsIHByb3ZpZGluZyBhIHN0
b3JhZ2UgYXJlYSAoLUQpLCB0aGUgY29ubmVjdGlvbgp0ZXN0IHVzZXMgYSBo
YXJkY29kZWQgZGJuYW1lIChkYm5hbWU9cG9zdGdyZXMpLCBjYXVzaW5nIGFu
IGVycm9yIG1lc3NhZ2U6DQoNCm5vIHBnX2hiYS5jb25mIGVudHJ5IGZvciBo
b3N0ICJbbG9jYWxdIiwgdXNlciAieHh4eHgiLCBkYXRhYmFzZSAicG9zdGdy
ZXMiLApTU0wgb2ZmDQoNCkJlY2F1c2Ugd2UgZGVsZXRlZCB0aGF0IERCLiBU
aGVyZSBpcyBubyB3YXkgdG8gZGVmaW5lIGEgZGlmZmVyZW50IERCIHRvIHRl
c3QKdGhlIGNvbm5lY3Rpb24uDQpJcyB0aGUgZGVsZXRpb24gb2YgcG9zdGdy
ZXMgREIgc3VwcG9ydGVkPw0KVGhpcyBjYXVzZXMgdGhlIGVycm9yIG1lc3Nh
Z2UgdG8gYXBwZWFyIGJ1dCBwb3N0Z3Jlc3FsIHN0YXJ0cyBPSyBhbiB3ZSBj
YW4KY29ubmVjdCB0byBvdXIgREIgd2l0aCBubyBpc3N1ZXMsIGJ1dCB3ZSdk
IGxpa2UgdG8gYXZvaWQgcXVlc3Rpb25zIGFib3V0IHRoZQplcnJvciBtZXNz
YWdlLgoK

hernan.bazan@intel.com writes:
> When calling "pg_ctl start", providing a storage area (-D), the connection
> test uses a hardcoded dbname (dbname=postgres), causing an error message:
> no pg_hba.conf entry for host "[local]", user "xxxxx", database "postgres",
> SSL off
> Because we deleted that DB. There is no way to define a different DB to test
> the connection.
> Is the deletion of postgres DB supported?

Not really.  You can do it but you will have operational annoyances like
that one, and probably not only from pg_ctl.  I'd suggest recreating it.

            regards, tom lane

We deleted that DB on our hardening process, we don't need it so there's no=
 reason to have it there.
What other issues can we have because we don't have that DB?

We deleted that DB on our hardening process, we don't need it so there's no=
 reason to have it there.
What other issues can we have because we don't have that DB?