Feedback-ID: i76984098:Fastmail
Message-ID: <78328b08-249e-4251-8a10-b5dac183442a@aklaver.com>
Date: Thu, 5 Mar 2026 08:04:36 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Index (primary key) corrupt?
To: Wim Rouquart <wim.rouquart@kbc.be>,
 Greg Sabino Mullane <htamfids@gmail.com>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
References: <AS2PR05MB1075477BA334D4DA262AD75BFEF16A@AS2PR05MB10754.eurprd05.prod.outlook.com>
 <AS2PR05MB10754BFE319E2594C9E076EE2EFFDA@AS2PR05MB10754.eurprd05.prod.outlook.com>
 <b812d3b4-b471-479c-b22a-2380fd3ab984@aklaver.com>
 <AS2PR05MB107549DDE42DC0B8E31CB52BFEF90A@AS2PR05MB10754.eurprd05.prod.outlook.com>
 <5043ff13-2f39-4a80-a8f8-6765746b6a89@aklaver.com>
 <AS2PR05MB10754EE81F34146EE8972713EEF91A@AS2PR05MB10754.eurprd05.prod.outlook.com>
 <58221272-d684-4799-a113-d5a5031a0b05@aklaver.com>
 <AS2PR05MB107541E760AECB8639BB968B5EF63A@AS2PR05MB10754.eurprd05.prod.outlook.com>
 <fd548bde-54d3-426a-a2b6-058750cfb554@aklaver.com>
 <AS2PR05MB1075432E74AF2FA975B02519AEF61A@AS2PR05MB10754.eurprd05.prod.outlook.com>
 <b1fec029-b8fb-4177-a01a-9457e813ce68@aklaver.com>
 <AS2PR05MB107546BEE7B8092148A0B51A0EF61A@AS2PR05MB10754.eurprd05.prod.outlook.com>
 <25b5291f-a3d3-4655-a3d3-57f28b70ec5a@aklaver.com>
 <AS2PR05MB107546C1B04FC4B3CCF32E60CEF7DA@AS2PR05MB10754.eurprd05.prod.outlook.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <AS2PR05MB107546C1B04FC4B3CCF32E60CEF7DA@AS2PR05MB10754.eurprd05.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/78328b08-249e-4251-8a10-b5dac183442a%40aklaver.com>
Precedence: bulk

On 3/5/26 5:23 AM, Wim Rouquart wrote:
> Internal
> 
>> So the REINDEX on the source PK is prompted by it not showing up on the target?
> 
> That's how we noticed the initial issue yes, we got errors during the datarefresh on the target  database where foreign keys wanted to reference the non-existing index (because it wasn't imported).
> 
>> On the test instance you set up with pg_basebackup and that has the corrupted index what happens if you try to INSERT a record with a duplicate id?
> 
> Good question, as I kind of expected, it doesn't complain at all when I do an insert with a duplicate id (and the row actually gets inserted). If I consecutively try to do the reindex, then I get the error that it can't because of doubles...
> 
> 
> -----Original Message-----
> From: Adrian Klaver <adrian.klaver@aklaver.com>
> Sent: vrijdag 13 februari 2026 18:33
> To: Wim Rouquart <wim.rouquart@kbc.be>; Greg Sabino Mullane <htamfids@gmail.com>
> Cc: pgsql-general@lists.postgresql.org
> Subject: Re: Index (primary key) corrupt?
> 
> 
> 
> The real sender of this external email is adrian.klaver@aklaver.com
> 
> 
> 
> 
> 
> 
> On 2/13/26 8:27 AM, Wim Rouquart wrote:
>> Internal
>>
>> 1) ) It won't be included with the CREATE TABLE statement per:-
>>
>> Yes, let's keep it at: it's not in the dumpfile anywhere.
>>
>>> 2) The issue seems to be not the dump, but the non-functional state of the index on the source database.
>>
>>> Is there any indication of why that is happening?
>>
>> Not as far as I know.
> 
> So the REINDEX on the source PK is prompted by it not showing up on the target?
> 
>>
>>> Also what error do you get on the source database that tells you the PK is not working?
>>
>> None, only noticed the issue because of the datarefresh to another instance where it turned out the primary key was not created in the target (because it was not in the dumpfile).
> 
> On the test instance you set up with pg_basebackup and that has the corrupted index what happens if you try to INSERT a record with a duplicate id?

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.

Just to be clear we are talking about this table:

CREATE TABLE bcf_work_type (
         id bigserial NOT NULL,
         aml_score int8 NOT NULL,
         CONSTRAINT idx_376814_primary PRIMARY KEY (id)
);

What is the use pattern for this table?

As I recall this is not a large table, but for completeness what is it's 
average size?

What are the Postgres log settings, on the source database, for?:

log_min_messages

log_min_error_statement

log_error_verbosity

log_statement

Are there any entries in the Postgres log that reference this table?

> 
>>
> 
>>> I hope this clears out any confusion.
>>>
>>> -----Original Message-----
>> Adrian Klaver
>> adrian.klaver@aklaver.com
>>
>> Disclaimer <https://www.kbc.com/KBCmailDisclaimer>
> 
> 
> Disclaimer <https://www.kbc.com/KBCmailDisclaimer>


-- 
Adrian Klaver
adrian.klaver@aklaver.com