Date: Sun, 28 Jul 2019 21:21:51 +0200
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Tomas Vondra <tv@fuzzy.cz>,
	Dean Rasheed <dean.a.rasheed@gmail.com>,
	pgsql-hackers@postgresql.org
Subject: Re: ANALYZE: ERROR:  tuple already updated by self
Message-ID: <20190728192151.wktk6htdixsjpt6x@development>
References: <20190618231233.GA27470@telsasoft.com>
 <20190618234858.GK16019@telsasoft.com>
 <20190619000837.awy6j7h45ahd4vop@alap3.anarazel.de>
 <20190723200127.moumhmj3z4b4dohg@alap3.anarazel.de>
 <20190728101520.da5nptiftmsnmv7c@development>
 <20190728164244.44eskwbamhlj6umf@alap3.anarazel.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <20190728164244.44eskwbamhlj6umf@alap3.anarazel.de>
User-Agent: NeoMutt/20180716-1444-295967
Precedence: bulk

On Sun, Jul 28, 2019 at 09:42:44AM -0700, Andres Freund wrote:
>Hi,
>
>On 2019-07-28 12:15:20 +0200, Tomas Vondra wrote:
>> Attached is a patch fixing the error by not building extended stats for
>> the inh=true case (as already proposed in this thread). That's about the
>> simplest way to resolve this issue for v12. It should add a simple
>> regression test too, I guess.
>
>Doesn't this also apply to v11?
>

AFAICS it applies to 10+ versions, because that's where extended stats
were introduced. We certainly can't mess with catalogs there, so this is
about the only backpatchable fix I can think of.

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services