| From: | Torsten Krah <krah(dot)tm(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index" |
| Date: | 2023-09-06 07:46:52 |
| Message-ID: | 959e9b03415d2ac683d67059f74d0377f64b03f4.camel@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daulat | 2023-09-06 08:05:16 | Postgres partition max limit |
| Previous Message | Lorusso Domenico | 2023-09-05 22:37:36 | Re: Efficient Partitioning Strategies for PostgreSQL Table with KSUID and High Volume |