pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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: Sun, 28 Jul 2019 21:21:51 +0200
Message-ID: <20190728192151.wktk6htdixsjpt6x@development> (raw)
In-Reply-To: <20190728164244.44eskwbamhlj6umf@alap3.anarazel.de>
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>

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 





view thread (20+ messages)  latest in thread

Message-ID: <20190728192151.wktk6htdixsjpt6x@development>
Permalink:  ../20190728192151.wktk6htdixsjpt6x@development/
Also on:    postgresql.org/message-id/20190728192151.wktk6htdixsjpt6x@development

 · 

reply

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: <20190728192151.wktk6htdixsjpt6x@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