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

From Andres Freund
Subject Re: ANALYZE: ERROR: tuple already updated by self
Date
Msg-id 20190729045320.ffwc7seez6nbmfaj@alap3.anarazel.de
Whole thread Raw
In response to Re: ANALYZE: ERROR: tuple already updated by self  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: ANALYZE: ERROR: tuple already updated by self  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
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.

- Andres



pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: COPY command on a table column marked as GENERATED ALWAYS
Next
From: Fabien COELHO
Date:
Subject: Re: refactoring - share str2*int64 functions