Re: ANALYZE: ERROR: tuple already updated by self - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: ANALYZE: ERROR: tuple already updated by self
Date
Msg-id 20190728192151.wktk6htdixsjpt6x@development
Whole thread Raw
In response to Re: ANALYZE: ERROR: tuple already updated by self  (Andres Freund <andres@anarazel.de>)
Responses Re: ANALYZE: ERROR: tuple already updated by self  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
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 



pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: Index Skip Scan
Next
From: Tom Lane
Date:
Subject: Re: how to run encoding-dependent tests by default