Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ehjDZ-0001QG-09 for pgsql-bugs@arkaria.postgresql.org; Fri, 02 Feb 2018 21:49:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ehjDX-0005YB-5u for pgsql-bugs@arkaria.postgresql.org; Fri, 02 Feb 2018 21:49:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ehjDX-0005Y1-09 for pgsql-bugs@lists.postgresql.org; Fri, 02 Feb 2018 21:49:55 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ehjDP-0004aY-7D for pgsql-bugs@postgresql.org; Fri, 02 Feb 2018 21:49:54 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id E416D2250B; Fri, 2 Feb 2018 16:49:44 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Fri, 02 Feb 2018 16:49:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=X9sN1b gWb2HwUkRUPHaTJCtT9ReMw6mbkUSWsjTpnW0=; b=lsvCmj0Z1dLfhUG5G5nY5k gRCUa+RREN3o1+M6DRFLeK764hsHikObjYH16O3qBdSYHpY1yuWQ8qi4AOPXNcWq assPGAJOp44knAvc1dEOk0VSpTvyZKROr6xouDLjS0SsftuSRCZUNXtzJFWeLG9s +bzf4GBufJT5HVITzZzqZs1tkYVujHNLob+d5gavVVWME0sAqpn4xiMugFBBW7Xn zulH8vLbMYMr6q3IsnEPJX433ASobFm8fWzczD0f+CahNSaGM9gYZEm3cXOG3m3y fO8878sXcsUk3GB6kZUAXJubihGLlsHLo804i0rUDCj8Pjz5nCWTNwXeGRmJ5mfw == X-ME-Sender: Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 87355249F1; Fri, 2 Feb 2018 16:49:44 -0500 (EST) Subject: Re: BUG #14912: Undocumented: 'psql -l' assumes database 'postgresql' not $USER To: "David G. Johnston" , mhwood@ameritech.net References: <20171116171735.1474.30450@wrigleys.postgresql.org> Cc: "pgsql-bugs@postgresql.org" From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <54c57675-f673-3f8e-d7d7-b5c61943f9fc@2ndquadrant.com> Date: Fri, 2 Feb 2018 16:49:44 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 postgres database, not the user's, > +      will be targeted for connection. This is similar to the meta-command >        \list. 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