Re: ANALYZE: ERROR: tuple already updated by self

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ANALYZE: ERROR: tuple already updated by self
Date: 2019-06-19 00:38:34
Message-ID: 20190619003834.GA11006@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Adrian Klaver 2019-06-19 01:03:18 Re: psql UPDATE field [tab] expands to DEFAULT?
Previous Message Peter Geoghegan 2019-06-19 00:20:21 Re: ANALYZE: ERROR: tuple already updated by self