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 20190729101833.rw7imcmggcusbyu6@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
List pgsql-hackers
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.


thanks

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



pgsql-hackers by date:

Previous
From: Sehrope Sarkuni
Date:
Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and KeyManagement Service (KMS)
Next
From: Jehan-Guillaume de Rorthais
Date:
Subject: Re: Fetching timeline during recovery