Feedback-ID: i76984098:Fastmail
Message-ID: <b1fec029-b8fb-4177-a01a-9457e813ce68@aklaver.com>
Date: Fri, 13 Feb 2026 08:09:21 -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>
 <f3ea70b8-c822-4b0f-b564-5e73d34188d4@aklaver.com>
 <AS2PR05MB10754A51AB7FC85161189FF7CEF11A@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>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <AS2PR05MB1075432E74AF2FA975B02519AEF61A@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/b1fec029-b8fb-4177-a01a-9457e813ce68%40aklaver.com>
Precedence: bulk

On 2/13/26 00:08, Wim Rouquart wrote:
> Internal
> 
> Ok, to do a small recap because indeed this thread has been extended for a while now.
> 
> - The issue with the specific index was noted on a production database (after a datarefresh that partly failed because of the missing index).
> 
> - To reproduce and experiment with the issue, a pg_basebackup was taken from that prod instance and restored to a test instance. Every single test step is executed on this test instance, the prod database is no longer involved, pg_basebackup is no longer involved, everything is pg_dump based from here on onwards.
> 
> - So this means the test pg_dumps where done with the index in a 'non-fuctional state'. As expected, the create statement of the index does NOT show up in the generated .sql scripts (neither 'loose' nor in the create statement of the table).

1) It won't be included with the CREATE TABLE statement per:-

https://www.postgresql.org/docs/current/app-pgdump.html

"--section=sectionname

     Only dump the named section. The section name can be pre-data, 
data, or post-data. This option can be specified more than once to 
select multiple sections. The default is to dump all sections.

     The data section contains actual table data, large-object contents, 
sequence values, and statistics for tables, materialized views, and 
foreign tables. Post-data items include definitions of indexes, 
triggers, rules, statistics for indexes, and constraints other than 
validated check and not-null constraints. Pre-data items include all 
other data definition items.
"
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?

Also what error do you get on the source database that tells you the PK 
is not working?


> 
> I hope this clears out any confusion.
> 
> -----Original Message-----
Adrian Klaver
adrian.klaver@aklaver.com