Feedback-ID: i76984098:Fastmail
Message-ID: <bf9f2217-103f-4737-b3cd-4795032a1242@aklaver.com>
Date: Tue, 10 Mar 2026 08:09:34 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Index (primary key) corrupt?
To: Greg Sabino Mullane <htamfids@gmail.com>,
 Wim Rouquart <wim.rouquart@kbc.be>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
References: <AS2PR05MB1075477BA334D4DA262AD75BFEF16A@AS2PR05MB10754.eurprd05.prod.outlook.com>
 <25b5291f-a3d3-4655-a3d3-57f28b70ec5a@aklaver.com>
 <AS2PR05MB107546C1B04FC4B3CCF32E60CEF7DA@AS2PR05MB10754.eurprd05.prod.outlook.com>
 <78328b08-249e-4251-8a10-b5dac183442a@aklaver.com>
 <DB5PR05MB107646FFE78759D1D5431F802EF7AA@DB5PR05MB10764.eurprd05.prod.outlook.com>
 <0868c260-9812-4629-b32d-026c1fe6089f@aklaver.com>
 <AS2PR05MB1075476F648651C8CC02D8048EF79A@AS2PR05MB10754.eurprd05.prod.outlook.com>
 <CAKAnmmLsxdt51sp-w0JxMi0haGXHFKD2pXURfOSOa5iVzjni4w@mail.gmail.com>
 <7d455186-0cba-4fd5-9f9e-7051627b3ae3@aklaver.com>
 <CAKAnmmJzw9TeOd=_VtJ430_AhS+asfRLuOg=mgL0yT_K+7X-yQ@mail.gmail.com>
 <2016a784-0644-4932-a0f1-3613c2521c78@aklaver.com>
 <CAKAnmmJogm0T4vF5nvhzK=GbfAcPhsLtKR_yRn-neMQP7S2_YQ@mail.gmail.com>
 <AS2PR05MB10754848BE9C45CEF4F881D5AEF46A@AS2PR05MB10754.eurprd05.prod.outlook.com>
 <CAKAnmmKwGsCtCeQ2GvDVhp9ZTjSsoZBrfe1Yw_UfcHD1u=StUw@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAKAnmmKwGsCtCeQ2GvDVhp9ZTjSsoZBrfe1Yw_UfcHD1u=StUw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/bf9f2217-103f-4737-b3cd-4795032a1242%40aklaver.com>
Precedence: bulk

On 3/10/26 7:43 AM, Greg Sabino Mullane wrote:
> On Tue, Mar 10, 2026 at 10:24 AM Wim Rouquart <wim.rouquart@kbc.be 
> <mailto:wim.rouquart@kbc.be>> wrote:
> 
>     Let me get this straight, are you still contesting that the index is
>     actually not part of the dumpfile and I somehow just keep on
>     ‘missing it’?
> 
> That is one possibility, yes, but there are others. We just don't have 
> enough data. It would be great to see exactly what pg_dump is doing so 
> we know where the corruption/disconnect is. If you have access, could 
> you try:

I am convinced that the index definition is not in the pg_dump output. 
The crux of the matter seems to be from here:

https://www.postgresql.org/message-id/78328b08-249e-4251-8a10-b5dac183442a%40aklaver.com

"Alright, so the corrupt index is transferred by the binary
pg_basebackup, but not in logical backups done via pg_dump/pg_restore.
The issue then is on the source database with whatever process is
corrupting the index and causing no error to be thrown when the table is
dumped."

Where the pg_basebackup was done from the production database in order 
to set up a test database and the logical dumps where done from the test 
database.

Hopefully the below will tease that out.

> 
> psql -c "alter system set log_statement='all' " -c "select pg_reload_conf()"
> 
> pg_dump -t bcf_work_type --schema-only > bcf.debug
> 
> psql -c "alter system reset log_statement" -c "select pg_reload_conf()"
> 
> Then send us bcf.debug as well as the Postgres logs generated during 
> that request?
> 
> Cheers,
> Greg
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com