BUG #14312: Hardcoded dbname on test_postmaster_connection
The following bug has been logged on the website:
Bug reference: 14312
Logged by: Hernan Bazan
Email address: hernan.bazan@intel.com
PostgreSQL version: 9.3.14
Operating system: MLOS
Description:
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?
This causes the error message to appear but postgresql starts OK an we can
connect to our DB with no issues, but we'd like to avoid questions about the
error message.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
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?
Import Notes
Resolved by subject fallback