From: Torsten Krah <krah.tm@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"
Date: Wed, 06 Sep 2023 09:46:52 +0200
Message-ID: <959e9b03415d2ac683d67059f74d0377f64b03f4.camel@gmail.com> (raw)
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
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: krah.tm@gmail.com
Subject: Re: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"
In-Reply-To: <959e9b03415d2ac683d67059f74d0377f64b03f4.camel@gmail.com>
References: <959e9b03415d2ac683d67059f74d0377f64b03f4.camel@gmail.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