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 1hcalP-00032n-SN for pgsql-committers@arkaria.postgresql.org; Sun, 16 Jun 2019 19:24:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hcalN-0003Dm-SU for pgsql-committers@arkaria.postgresql.org; Sun, 16 Jun 2019 19:24:25 +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 1hcalM-0003Dd-ME for pgsql-committers@lists.postgresql.org; Sun, 16 Jun 2019 19:24:24 +0000 Received: from mail-wm1-x344.google.com ([2a00:1450:4864:20::344]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hcalF-0000kJ-3N for pgsql-committers@lists.postgresql.org; Sun, 16 Jun 2019 19:24:23 +0000 Received: by mail-wm1-x344.google.com with SMTP id f17so4365852wme.2 for ; Sun, 16 Jun 2019 12:24:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=JRNli0iL9exa8Tf6xLgN+dwTCv4MzWrIZp5BzqHeLRQ=; b=GKJSuHubE95HHKx6p6M5mnzZtTe2njfXlHPOkQ62SUKJncG4217BgQZiae9fTxpd9l RQ69DgypAThCvy0sDHIfOsJSSXd2mfRKxMPQXYgnypOsz6sw0x8AWy9DIjCYZYXAFhOl pOou3kYcA6ocWtRGB7GvrT9lqgl6RLCi5iaOjxvT6mkz3ZNbWFX06gRuPKAfenB7HT92 JahRDB+wCdxNAJoX/qD6udlwMyG676GlZ2V83dDqrUulMJ7F67H4v6kb9w27cmg/p4of xoI0vXPjwbWm7UeQ+UhoOkU0jYkgC99w/oUz+TNx206SpwhKYnFu2EaUQZTc9Eyj9wVl FMUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=JRNli0iL9exa8Tf6xLgN+dwTCv4MzWrIZp5BzqHeLRQ=; b=nWkvGx+mYFCRIqkxiKgR5LCeen8ar4lUbMlxK1/Xe34NDhzhJctzDhOW1FruQ99YBs QfZDMzTzy80AXEHt84t+c91UxZj63dPn/edbTqaudLou5rCChaazZw/V95E0EdQY2MbE Pu6QpwLrVWo095uNUzxqTjxzVdPRhr8IPCGwTgq8Zn583urqbPz49DAjlImaJ0PzOPim XuQB3cRj5yES28gFMb+aBkefvxg/VyCaUpfPXzuANwwi7bX/0bt2frG2doh3lClqtRl+ +ZWfuSbZviUsBmCXdz1NHT37tO9vw97xg0fsZex2U06PDwXot/04Mmuz+q0sXWFE7Bvb oL2w== X-Gm-Message-State: APjAAAWzU6n+y5foFFbX9URasqLHF8UdJ3KZZwwHUI9PesF8DcNmaUQ7 UF5t8arUoCFS4JEatMe3M9750g== X-Google-Smtp-Source: APXvYqy5aETACF0dJCau+EiR46Y1r5UuHBu4V+2id44s1pG7Yhy7NOnxvntvGlliXXY+jHvCVMuDxg== X-Received: by 2002:a7b:c081:: with SMTP id r1mr6613974wmh.76.1560713055243; Sun, 16 Jun 2019 12:24:15 -0700 (PDT) Received: from localhost (ip-86-49-243-43.net.upcbroadband.cz. [86.49.243.43]) by smtp.gmail.com with ESMTPSA id s7sm6015914wmc.2.2019.06.16.12.24.14 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Sun, 16 Jun 2019 12:24:14 -0700 (PDT) Date: Sun, 16 Jun 2019 21:24:12 +0200 From: Tomas Vondra To: Tom Lane Cc: Fabien COELHO , Dean Rasheed , Tomas Vondra , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Rework the pg_statistic_ext catalog Message-ID: <20190616192412.yrgjlak3opex2ubh@development> 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> <6390.1560707523@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <6390.1560707523@sss.pgh.pa.us> User-Agent: NeoMutt/20180716-1444-295967 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sun, Jun 16, 2019 at 01:52:03PM -0400, Tom Lane wrote: >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 ...) > FWIW I'm not using anything bleeding edge either (gcc from fedora 29, 8.3.1 to be exact), no ccache. And I can't reproduce it anymore, so I agree it might have been some stale state after catversion bump. Although I usually do make-clean before running tests ... regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services