Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hpbLB-0004mA-1f for pgsql-hackers@arkaria.postgresql.org; Mon, 22 Jul 2019 16:39:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hpbL9-0000yN-MZ for pgsql-hackers@arkaria.postgresql.org; Mon, 22 Jul 2019 16:39:07 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hpbL9-0000yG-AS for pgsql-hackers@lists.postgresql.org; Mon, 22 Jul 2019 16:39:07 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1hpbL7-0007uT-3Q for pgsql-hackers@lists.postgresql.org; Mon, 22 Jul 2019 16:39:06 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x6MGd1As027725; Mon, 22 Jul 2019 12:39:01 -0400 From: Tom Lane To: Peter Eisentraut cc: Andrew Dunstan , pgsql-hackers@lists.postgresql.org Subject: Re: initdb recommendations In-reply-to: <7886.1563812705@sss.pgh.pa.us> References: <20190406180839.GA1921989@rfd.leadboat.com> <96389374-9454-d26d-6f79-7c7b15ec14bd@2ndquadrant.com> <91f8272f-117f-2a04-862b-871a7b86eeed@2ndquadrant.com> <7b6c4220-e5ef-2a13-18ad-af596c52b71a@2ndquadrant.com> <23654.1563804669@sss.pgh.pa.us> <7886.1563812705@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Mon, 22 Jul 2019 12:25:05 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <27723.1563813541.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 22 Jul 2019 12:39:01 -0400 Message-ID: <27724.1563813541@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I wrote: > I'm afraid we're going to have to revert this, at least till > such time as a fixed buildfarm client is in universal use. > As for the nature of that fix, I don't quite understand why > the forced -U is there --- maybe we could just remove it? > But there are multiple places in the buildfarm client that > have hard-wired references to "buildfarm". BTW, it looks like the Windows buildfarm critters have a separate problem: they're failing with initdb: error: must specify a password for the superuser to enable md5 aut= hentication One would imagine that even if we'd given a password to initdb, subsequent connection attempts would fail for lack of a password. There might not be any practical fix except forcing trust auth for the Windows critters. regards, tom lane