Re: ANALYZE: ERROR: tuple already updated by self

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Tomas Vondra <tv(at)fuzzy(dot)cz>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: ANALYZE: ERROR: tuple already updated by self
Date: 2019-07-29 10:18:33
Message-ID: 20190729101833.rw7imcmggcusbyu6@development
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Sun, Jul 28, 2019 at 09:53:20PM -0700, Andres Freund wrote:
>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.


Tomas Vondra
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Jehan-Guillaume de Rorthais 2019-07-29 10:26:31 Re: Fetching timeline during recovery
Previous Message Sehrope Sarkuni 2019-07-29 10:17:27 Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)