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 1ei0KE-0006NK-9a for pgsql-bugs@arkaria.postgresql.org; Sat, 03 Feb 2018 16:05:58 +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 1ei0KD-0007rT-8k for pgsql-bugs@arkaria.postgresql.org; Sat, 03 Feb 2018 16:05:57 +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 1ei0KC-0007rI-Qc for pgsql-bugs@lists.postgresql.org; Sat, 03 Feb 2018 16:05:57 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ei0K9-0002Nl-9R for pgsql-bugs@postgresql.org; Sat, 03 Feb 2018 16:05:56 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 08CAC226B5; Sat, 3 Feb 2018 11:05:51 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Sat, 03 Feb 2018 11:05:51 -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=gPrz7S 9IflVRwzbTkZu4XuwmWR3ISJE6TI3UR8KgyAU=; b=h1pG84Qrz6y4QnbyFJmTqk yeotBcWwdcmGnhzPzytPYX9rf8P2/mXN0BT1san4iTmJ6+t3ZFQYbC4yepY48ARA gbNwLgLtNT8dqzjDwygT12A/zFVzuTP80nDntOu/K+YAi46Q5J28186gkAV1NViH ja+rOsyogq7BkeFXA9a6jI8pWtJqIdH/IrwrDh06khR8GFoqpgwTSEViZ0Vy9MdD 2bauoFN9xFkEXhBl2u7vbJO5o2CSGBVYLJ0w/p/AhuTcm/+zIXDURoiyY0fz8onz FPIf2g+RmRfTUUXngbA1s2D1XuzkxnlZeATfDp4Dw/cYupdAhCYEE0164D1olFJw == X-ME-Sender: Received: from april.local (unknown [216.162.94.2]) by mail.messagingengine.com (Postfix) with ESMTPA id B6DF87E12E; Sat, 3 Feb 2018 11:05:50 -0500 (EST) Subject: Re: BUG #14912: Undocumented: 'psql -l' assumes database 'postgresql' not $USER To: "David G. Johnston" References: <20171116171735.1474.30450@wrigleys.postgresql.org> <54c57675-f673-3f8e-d7d7-b5c61943f9fc@2ndquadrant.com> Cc: Mark Wood , "pgsql-bugs@postgresql.org" From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Sat, 3 Feb 2018 11:05:41 -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 2/2/18 17:05, David G. Johnston wrote: > What does "an explicit database name is not found" mean? > > ​A name was not supplied to the psql command either as the first > non-option argument, via the --dbname command line option, in the > connection URI (possibly indirectly via a pg_service.conf entry), or via > the PGDATABASE environment variable. OK, clarified that a bit further. Actually, an environment variable does not take any effect for this. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services