pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Dean Rasheed <dean.a.rasheed@gmail.com>
Cc: Tomas Vondra <tomas.vondra@postgresql.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Rework the pg_statistic_ext catalog
Date: Sun, 16 Jun 2019 21:24:12 +0200
Message-ID: <20190616192412.yrgjlak3opex2ubh@development> (raw)
In-Reply-To: <6390.1560707523@sss.pgh.pa.us>
References: <8833.1560647898@sss.pgh.pa.us>
	<20156.1560650744@sss.pgh.pa.us>
	<CAEZATCWWX5O57d=MHY=MqyJe-xHG2pbi75LKLjo6aZLP3zsaow@mail.gmail.com>
	<20190616085651.d2hxuiqlojewed5j@development>
	<20190616100328.shl2hhuy2pup6ges@development>
	<20190616112021.2mncnuj26sbsbnzx@development>
	<14081.1560693790@sss.pgh.pa.us>
	<4352.1560698164@sss.pgh.pa.us>
	<alpine.DEB.2.21.1906161933240.21115@lancre>
	<6390.1560707523@sss.pgh.pa.us>

On Sun, Jun 16, 2019 at 01:52:03PM -0400, Tom Lane wrote:
>Fabien COELHO <coelho@cri.ensmp.fr> 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 





view thread (13+ messages)

Message-ID: <20190616192412.yrgjlak3opex2ubh@development>
Permalink:  ../20190616192412.yrgjlak3opex2ubh@development/
Also on:    postgresql.org/message-id/20190616192412.yrgjlak3opex2ubh@development

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: tomas.vondra@2ndquadrant.com, tgl@sss.pgh.pa.us, coelho@cri.ensmp.fr, dean.a.rasheed@gmail.com, tomas.vondra@postgresql.org, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Rework the pg_statistic_ext catalog
  In-Reply-To: <20190616192412.yrgjlak3opex2ubh@development>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox