Re: BUG #14912: Undocumented: 'psql -l' assumes database 'postgresql' not $USER

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, mhwood(at)ameritech(dot)net
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14912: Undocumented: 'psql -l' assumes database 'postgresql' not $USER
Date: 2018-02-02 21:49:44
Message-ID: 54c57675-f673-3f8e-d7d7-b5c61943f9fc@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 11/16/17 16:27, David G. Johnston wrote:
>        List all available databases, then exit. Other non-connection
> -      options are ignored. This is similar to the meta-command
> +      options are ignored. If an explicit database name is not
> +      found the <literal>postgres</literal> database, not the user's,
> +      will be targeted for connection. This is similar to the meta-command
>        <command>\list</command>.

What does "an explicit database name is not found" mean? How does one
find an explicit database name?

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2018-02-02 22:05:36 Re: BUG #14912: Undocumented: 'psql -l' assumes database 'postgresql' not $USER
Previous Message Peter Eisentraut 2018-02-02 20:15:23 Re: BUG #14952: COPY fails to fill in IDENTITY column default value