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 1hpb7j-0003y4-8E for pgsql-hackers@arkaria.postgresql.org; Mon, 22 Jul 2019 16:25:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hpb7g-0003kq-Pc for pgsql-hackers@arkaria.postgresql.org; Mon, 22 Jul 2019 16:25:12 +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 1hpb7g-0003kj-Df for pgsql-hackers@lists.postgresql.org; Mon, 22 Jul 2019 16:25:12 +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 1hpb7e-0007n9-4Q for pgsql-hackers@lists.postgresql.org; Mon, 22 Jul 2019 16:25:11 +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 x6MGP5QI007887; Mon, 22 Jul 2019 12:25:05 -0400 From: Tom Lane To: Peter Eisentraut cc: Andrew Dunstan , pgsql-hackers@lists.postgresql.org Subject: Re: initdb recommendations In-reply-to: <23654.1563804669@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> Comments: In-reply-to Tom Lane message dated "Mon, 22 Jul 2019 10:11:09 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7885.1563812705.1@sss.pgh.pa.us> Date: Mon, 22 Jul 2019 12:25:05 -0400 Message-ID: <7886.1563812705@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I wrote: > Peter Eisentraut writes: >> Pushed with that note. Thanks. > This has completely broken the buildfarm. On inspection, it seems the reason for that is that the buildfarm script runs initdb with '-U buildfarm', so that peer-auth connections will only work if the buildfarm is being run by an OS user named exactly "buildfarm". That happens to be true on my macOS animals, which is why they're not broken ... but apparently, nobody else does it that way. 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". regards, tom lane