From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Tomas Vondra <tv@fuzzy.cz>
Cc: Dean Rasheed <dean.a.rasheed@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: ANALYZE: ERROR: tuple already updated by self
Date: Tue, 30 Jul 2019 20:11:34 +0200
Message-ID: <20190730181134.3d6t6yd6rnmoeuv3@development> (raw)
In-Reply-To: <20190729101833.rw7imcmggcusbyu6@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>
<20190728192151.wktk6htdixsjpt6x@development>
<20190729045320.ffwc7seez6nbmfaj@alap3.anarazel.de>
<20190729101833.rw7imcmggcusbyu6@development>
On Mon, Jul 29, 2019 at 12:18:33PM +0200, Tomas Vondra wrote:
>On Sun, Jul 28, 2019 at 09:53:20PM -0700, Andres Freund wrote:
>>Hi,
>>
>>On 2019-07-28 21:21:51 +0200, Tomas Vondra wrote:
>>>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.
>>
>>AFAIU the inh version wouldn't be used anyway, and this has never
>>worked. So I think it's imo fine to fix it that way for < master. For
>>master we should have something better, even if perhaps not immediately.
>>
>
>Agreed. I'll get the simple fix committed soon, and put a TODO on my
>list for pg13.
>
I've pushed the simple fix - I've actually simplified it a bit further by
simply not calling the BuildRelationExtStatistics() at all when inh=true,
instead of passing the flag to BuildRelationExtStatistics() and making the
decision there. The function is part of public API, so this would be an
ABI break (although it's unlikely anyone else is calling the function).
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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-hackers@postgresql.org
Cc: tomas.vondra@2ndquadrant.com, andres@anarazel.de, pryzby@telsasoft.com, tv@fuzzy.cz, dean.a.rasheed@gmail.com
Subject: Re: ANALYZE: ERROR: tuple already updated by self
In-Reply-To: <20190730181134.3d6t6yd6rnmoeuv3@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