Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qdpGq-004rII-8T for pgsql-general@arkaria.postgresql.org; Wed, 06 Sep 2023 09:56:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qdpGp-008uEP-0i for pgsql-general@arkaria.postgresql.org; Wed, 06 Sep 2023 09:56:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qdpGo-008uEA-Hb for pgsql-general@lists.postgresql.org; Wed, 06 Sep 2023 09:56:22 +0000 Received: from mail-ej1-x630.google.com ([2a00:1450:4864:20::630]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qdpGl-0032Ki-1R for pgsql-general@lists.postgresql.org; Wed, 06 Sep 2023 09:56:21 +0000 Received: by mail-ej1-x630.google.com with SMTP id a640c23a62f3a-99bc9e3cbf1so163412466b.0 for ; Wed, 06 Sep 2023 02:56:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1693994177; x=1694598977; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=c4aaqYI4zgZSj8UU/9VfbrkQAuzEVKef5+rAGCEUYak=; b=JHTgLXULuBFSnQMvtTy6B149jcMsq6jgzCzE3mxoLUuX0rutU0f4VEhSXKAIcMkDvg CQyYvmompAxcjIdvsGEg1NVhLSlcK1c9XwIk1+eHoJAZmozLyaQbGmMvEUyLAZ/Ud/3i 5Ks8kkaezS1YRmVhzvBcrm+RSpMzThBbhCrj1ed8aD6EQ/IGhM4iquGwkwbPH/XShk9p KwNRtgetqf5IeslR/N5hIefsD3mkph3KM0YOuB5wCeYCnb4UfIfC4L5UBDMzfQulppTb bWGvKdl0P7KGXK/2hsZOjzQv5OE4IbBs69TnDo22R7Kq2vC1V9Lrp+M7Wzipci1mpkiL bvyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693994177; x=1694598977; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=c4aaqYI4zgZSj8UU/9VfbrkQAuzEVKef5+rAGCEUYak=; b=K5ky9+kf9Ww0gTudPdkDGT3ClizBLxRIjzLHRpGXvsWt3CPMRcGOnY8pqOrfMLoh+s 45Qj8Y2kKEamQcOtPRM7OPyhGWttj1YVQIXf9yCQMCt+7uN2QRtUv2yLNAMsJFl1AfmK V0HLEzkutIjySlUiyRGQBL3xlHDCm5aNZfCra4HK/dbCixCFgpBTDNyCZXPCubLL0Wax glgE5ogPzTB45dWhSvbvbPx1GuZxEOEmmKa+jQ9DzNhSiUGQsCxAl+aBNJbTtXVqYecb fiUDOHT6lyY/zLmrxcORGYoClotmqoEknfeBJ1R/HeJ/6wCSPbaMlAiUrEUU/EBwXgMu vWXg== X-Gm-Message-State: AOJu0Yy3y8Fwca3NlnBmevSeO7DKI2ks73iNbOQr2VwepMFJq9WHWrOH hHSifW//fWxlxkMnk3lNWjViJg== X-Google-Smtp-Source: AGHT+IHpbkc6zbTzDzmajjIsDwow5BO3WpsiE/Dr2F0B7hz8mD4rXI43d6tLAXGalh+wdLTuJJHF7Q== X-Received: by 2002:a17:907:2c6a:b0:9a5:d2f5:c76 with SMTP id ib10-20020a1709072c6a00b009a5d2f50c76mr2334663ejc.5.1693994176700; Wed, 06 Sep 2023 02:56:16 -0700 (PDT) Received: from localhost.localdomain (178-190-169-125.adsl.highway.telekom.at. [178.190.169.125]) by smtp.gmail.com with ESMTPSA id jw26-20020a17090776ba00b00982a92a849asm8837569ejc.91.2023.09.06.02.56.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 06 Sep 2023 02:56:16 -0700 (PDT) Message-ID: Subject: Re: running ANALYZE results in => duplicate key value violates unique constraint "pg_statistic_relid_att_inh_index" From: Laurenz Albe To: krah.tm@gmail.com, pgsql-general@lists.postgresql.org Date: Wed, 06 Sep 2023 11:56:15 +0200 In-Reply-To: <8af28a305839719a496be84d18c15a2525e954c8.camel@gmail.com> References: <959e9b03415d2ac683d67059f74d0377f64b03f4.camel@gmail.com> <914c8b13fe9c1fb41a3b673b59813a210c72c92f.camel@cybertec.at> <8af28a305839719a496be84d18c15a2525e954c8.camel@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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. >=20 > It is a test instance / container anyway which is deleted afterwards > and can be setup again as often as I want. >=20 > But how is that corruption happening - I mean it is a docker image, > freshly fetched from the registry. >=20 > After that I am starting a container from that image, (re)importing > data (different tests =3D> 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. >=20 > 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