Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l2OrH-0000oJ-He for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Jan 2021 01:33:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l2OrG-0003oo-Gr for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Jan 2021 01:33:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l2OrG-0003oe-A6 for pgsql-hackers@lists.postgresql.org; Thu, 21 Jan 2021 01:33:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l2Or9-00073v-8O for pgsql-hackers@postgresql.org; Thu, 21 Jan 2021 01:33:57 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 10L1XlnU798281; Wed, 20 Jan 2021 20:33:47 -0500 From: Tom Lane To: Robert Haas cc: "pgsql-hackers@postgresql.org" Subject: Re: strange error reporting In-reply-to: References: <717401.1611163169@sss.pgh.pa.us> <718535.1611164867@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Wed, 20 Jan 2021 12:59:21 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <798279.1611192827.1@sss.pgh.pa.us> Date: Wed, 20 Jan 2021 20:33:47 -0500 Message-ID: <798280.1611192827@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Robert Haas writes: >>> Maybe it would be better if it said: >>> connection to database at socket "/tmp/.s.PGSQL.5432" failed: FATAL: >>> database "rhaas" does not exist >> I'd be inclined to spell it "connection to server at ... failed", >> but that sort of wording is surely also possible. > "connection to server" rather than "connection to database" works for > me; in fact, I think I like it slightly better. If I don't hear any other opinions, I'll change these messages to "connection to server at socket \"%s\" failed: " "connection to server at \"%s\" (%s), port %s failed: " (or maybe "server on socket"? "at" sounds right for the IP address case, but it feels a little off in the socket pathname case.) regards, tom lane