From: Justin Pryzby <pryzby@telsasoft.com>
To: pgsql-hackers@postgresql.org
Subject: Re: ANALYZE: ERROR: tuple already updated by self
Date: Tue, 18 Jun 2019 19:38:34 -0500
Message-ID: <20190619003834.GA11006@telsasoft.com> (raw)
In-Reply-To: <20190618234858.GK16019@telsasoft.com>
References: <20190618231233.GA27470@telsasoft.com>
<20190618234858.GK16019@telsasoft.com>
On Tue, Jun 18, 2019 at 06:48:58PM -0500, Justin Pryzby wrote:
> On Tue, Jun 18, 2019 at 06:12:33PM -0500, Justin Pryzby wrote:
> > A customers DB crashed due to OOM. While investigating the issue in our
> > report, I created MV stats, which causes this error:
> >
> > ts=# CREATE STATISTICS sectors_stats (dependencies) ON site_id,sect_id FROM sectors;
> > CREATE STATISTICS
> > ts=# ANALYZE sectors;
> > ERROR: XX000: tuple already updated by self
> > LOCATION: simple_heap_update, heapam.c:4613
>
> > I'm guessing the issue is with pg_statistic_ext, which I haven't touched.
> >
> > Next step seems to be to truncate pg_statistic{,ext} and re-analyze the DB.
>
> Confirmed the issue is there.
>
> ts=# analyze sectors;
> ERROR: tuple already updated by self
> ts=# begin; delete from pg_statistic_ext; analyze sectors;
> BEGIN
> DELETE 87
> ANALYZE
Why this works seems to me to be unexplained..
Justin
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: pryzby@telsasoft.com
Subject: Re: ANALYZE: ERROR: tuple already updated by self
In-Reply-To: <20190619003834.GA11006@telsasoft.com>
* 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