Re: ANALYZE: ERROR: tuple already updated by self - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: ANALYZE: ERROR: tuple already updated by self
Date
Msg-id 20190619003834.GA11006@telsasoft.com
Whole thread Raw
In response to Re: ANALYZE: ERROR: tuple already updated by self  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: ANALYZE: ERROR: tuple already updated by self
List 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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: ANALYZE: ERROR: tuple already updated by self
Next
From: Andres Freund
Date:
Subject: Re: ANALYZE: ERROR: tuple already updated by self