Re: BUG #14312: Hardcoded dbname on test_postmaster_connection

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: hernan(dot)bazan(at)intel(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14312: Hardcoded dbname on test_postmaster_connection
Date: 2016-09-05 15:13:26
Message-ID: 10495.1473088406@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

hernan(dot)bazan(at)intel(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message coolman.peto 2016-09-05 16:31:58 BUG #14313: justify interval bug
Previous Message Tom Lane 2016-09-05 15:05:50 Re: BUG #14310: Triggers do not fire