pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
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 19:45:45 +0200 (CEST)
Message-ID: <alpine.DEB.2.21.1906161933240.21115@lancre> (raw)
In-Reply-To: <4352.1560698164@sss.pgh.pa.us>
References: <E1hcHz2-0005mY-5A@gemulon.postgresql.org>
	<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>


Hello Tom,

>> I see that Coelho's two bleeding-edge-clang animals are reporting that
>> failure too.  Normally I'd just ignore those two;

And you'd be right.

>> they break pretty regularly.  Maybe you're using an 
>> almost-bleeding-edge clang?
>
> Oh --- I managed to reproduce that failure locally on RHEL6 (nothing
> bleeding-edge anywhere), but it went away after make-clean-and-rebuild.

> I'm suspicious that the underlying cause was failure to recompile
> something that knows the value of CATALOG_VERSION_NO.

Hmmm. My animals compile out of the source tree, not sure how this could 
happen.

> 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.

-- 
Fabien.





view thread (13+ messages)  latest in thread

Message-ID: <alpine.DEB.2.21.1906161933240.21115@lancre>
Permalink:  ../alpine.DEB.2.21.1906161933240.21115@lancre/
Also on:    postgresql.org/message-id/alpine.DEB.2.21.1906161933240.21115@lancre

 · 

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: coelho@cri.ensmp.fr, tgl@sss.pgh.pa.us, tomas.vondra@2ndquadrant.com, 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: <alpine.DEB.2.21.1906161933240.21115@lancre>

* 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