From: Tom Lane <tgl@sss.pgh.pa.us>
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: Tue, 18 Jun 2019 20:16:50 -0400
Message-ID: <30099.1560903410@sss.pgh.pa.us> (raw)
In-Reply-To: <20190619000837.awy6j7h45ahd4vop@alap3.anarazel.de>
References: <20190618231233.GA27470@telsasoft.com>
<20190618234858.GK16019@telsasoft.com>
<20190619000837.awy6j7h45ahd4vop@alap3.anarazel.de>
Andres Freund <andres@anarazel.de> writes:
> I think the problem is pretty plainly that for inheritance tables we'll
> try to store extended statistics twice. And thus end up updating the
> same row twice.
They shouldn't be the same row though. If we're to try to capture
ext-stats on inheritance trees --- and I think that's likely a good
idea --- then we need a bool corresponding to pg_statistic's stainherit
as part of pg_statistic_ext's primary key.
Since there is no such bool there now, and I assume that nobody wants
yet another pg_statistic_ext-driven catversion bump for v12, the only
fix is to get the stats machinery to not compute or store such stats.
For now. But I think we ought to change that in v13.
regards, tom lane
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: tgl@sss.pgh.pa.us, 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: <30099.1560903410@sss.pgh.pa.us>
* 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