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 1hcZK8-0008Ay-T5 for pgsql-committers@arkaria.postgresql.org; Sun, 16 Jun 2019 17:52:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hcZK7-0006ur-IV for pgsql-committers@arkaria.postgresql.org; Sun, 16 Jun 2019 17:52:11 +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 1hcZK7-0006uk-8N for pgsql-committers@lists.postgresql.org; Sun, 16 Jun 2019 17:52:11 +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.89) (envelope-from ) id 1hcZK5-0008Kv-1L; Sun, 16 Jun 2019 17:52:10 +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 x5GHq3hx006391; Sun, 16 Jun 2019 13:52:03 -0400 From: Tom Lane To: Fabien COELHO cc: Tomas Vondra , Dean Rasheed , Tomas Vondra , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Rework the pg_statistic_ext catalog In-reply-to: References: <8833.1560647898@sss.pgh.pa.us> <20156.1560650744@sss.pgh.pa.us> <20190616085651.d2hxuiqlojewed5j@development> <20190616100328.shl2hhuy2pup6ges@development> <20190616112021.2mncnuj26sbsbnzx@development> <14081.1560693790@sss.pgh.pa.us> <4352.1560698164@sss.pgh.pa.us> Comments: In-reply-to Fabien COELHO message dated "Sun, 16 Jun 2019 19:45:45 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6389.1560707523.1@sss.pgh.pa.us> Date: Sun, 16 Jun 2019 13:52:03 -0400 Message-ID: <6390.1560707523@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Fabien COELHO writes: >> This theory is insufficient to explain why Coelho's animals failed, >> though. Maybe it would, if you also posit a ccache screwup? But it's >> not obvious from their configurations that they're using ccache at all. > Indeed, no ccache. The compilers change often (well, once a week), I do > not want anything kept across compiler versions. The animals are really > testing the compilers as much as they are testing postgres. > However, there is an autoconf cache, but I do not see why it would have > such an effect. > So no clue. And now they're both green again, so even less clue. Oh well. On another day I'd be interested to understand exactly what happened there, but right now I lack the time or energy to look closer. (I do still have a suspicion that it was somehow caused by the catversion bumps ...) regards, tom lane