running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index" - Mailing list pgsql-general

From Torsten Krah
Subject running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"
Date
Msg-id 959e9b03415d2ac683d67059f74d0377f64b03f4.camel@gmail.com
Whole thread Raw
Responses Re: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"
Re: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"
List pgsql-general
Hi,

I am running that one (official docker image)

PostgreSQL 13.11 (Debian 13.11-1.pgdg110+1) on x86_64-pc-linux-gnu,
compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit

and one of my nightly jobs reported that error yesterday when running
an "ANALYZE":

FEHLER: doppelter Schlüsselwert verletzt Unique-Constraint »pg_statistic_relid_att_inh_index«
  Detail: Schlüssel »(starelid, staattnum, stainherit)=(2609, 4, f)« existiert bereits.

which should translate to something like:

ERROR:  duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"
> DETAIL:  Key (starelid, staattnum, stainherit)=(2609, 4, f) already exists.


Anyone an idea what's wrong?

Maybe (not?) related but sometimes the analyze does fail with:

ERROR: attempted to delete invisible tuple


Both errors are only happening here and there - so I don't have a
reproducer, but still I am curious what is wrong here with me running
an "ANALYZE" after my data import.

thanks for insights :)

kind regards

Torsten




pgsql-general by date:

Previous
From: Lorusso Domenico
Date:
Subject: Re: Efficient Partitioning Strategies for PostgreSQL Table with KSUID and High Volume
Next
From: Daulat
Date:
Subject: Postgres partition max limit