From: Laurenz Albe <laurenz.albe@cybertec.at>
To: krah.tm@gmail.com
To: pgsql-general@lists.postgresql.org
Subject: Re: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index"
Date: Wed, 06 Sep 2023 11:56:15 +0200
Message-ID: <efd746b47ab0ac43c432c8f79383e4b1237f586e.camel@cybertec.at> (raw)
In-Reply-To: <8af28a305839719a496be84d18c15a2525e954c8.camel@gmail.com>
References: <959e9b03415d2ac683d67059f74d0377f64b03f4.camel@gmail.com>
<914c8b13fe9c1fb41a3b673b59813a210c72c92f.camel@cybertec.at>
<8af28a305839719a496be84d18c15a2525e954c8.camel@gmail.com>
On Wed, 2023-09-06 at 10:33 +0200, Torsten Krah wrote:
> Am Mittwoch, dem 06.09.2023 um 10:21 +0200 schrieb Laurenz Albe:
> > You are lucky that the corrupted table is one that holds data that
> > can be rebuilt.
>
> It is a test instance / container anyway which is deleted afterwards
> and can be setup again as often as I want.
>
> But how is that corruption happening - I mean it is a docker image,
> freshly fetched from the registry.
>
> After that I am starting a container from that image, (re)importing
> data (different tests => different data so the cycle of delete data /
> import data / analyze the data happens quite often) and running my
> tests.
> The OS does not report anything which would relate nor does any other
> tool / system fail nor does postgresl itself fail on any other table
> here - it always fails only on that analyze part.
>
> That happens all in about 8-10 minutes for the whole process - what is
> causing that corruption in that short timeframe here?
If you have a reproducible way to create the data corruption, that would
be very interesting. It micht be a software bug.
Yours,
Laurenz Albe
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: laurenz.albe@cybertec.at, 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: <efd746b47ab0ac43c432c8f79383e4b1237f586e.camel@cybertec.at>
References: <959e9b03415d2ac683d67059f74d0377f64b03f4.camel@gmail.com> <914c8b13fe9c1fb41a3b673b59813a210c72c92f.camel@cybertec.at> <8af28a305839719a496be84d18c15a2525e954c8.camel@gmail.com> <efd746b47ab0ac43c432c8f79383e4b1237f586e.camel@cybertec.at>
* 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