Feedback-ID: i76984098:Fastmail
Message-ID: <25b5291f-a3d3-4655-a3d3-57f28b70ec5a@aklaver.com>
Date: Fri, 13 Feb 2026 09:32:47 -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>
 <CAKAnmmLNaQ9NnjP=-kMj4t6wjt3+5nmMbQc2+F2Ekv_=zJWs5w@mail.gmail.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>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <AS2PR05MB107546BEE7B8092148A0B51A0EF61A@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/25b5291f-a3d3-4655-a3d3-57f28b70ec5a%40aklaver.com>
Precedence: bulk


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?

> 

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