Feedback-ID: i76984098:Fastmail
Message-ID: <fd548bde-54d3-426a-a2b6-058750cfb554@aklaver.com>
Date: Thu, 12 Feb 2026 08:25:28 -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>
 <1bfa0b6b-11a8-458f-a3f3-3f86574abc1d@aklaver.com>
 <AS2PR05MB107548567EEDAAB3AF74A6C59EF11A@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>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <AS2PR05MB107541E760AECB8639BB968B5EF63A@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/fd548bde-54d3-426a-a2b6-058750cfb554%40aklaver.com>
Precedence: bulk

On 2/11/26 01:05, Wim Rouquart wrote:
> Internal
> 
> I know the initial thread was started a while ago, but as was explained there the restore was done purely to have a playground db for this specific issue. I know the difference between pg_dump and pg_restore.
> The issue is with pg_dump, not with pg_basebackup (as is proven as pg_basebackup and then the restore perfectly transfers the 'situation' as is between the production database and the playground database).

Are you saying that you used pg_basebackp to create a test instance and 
then did a pg_dump from the test instance and used that output in a 
pg_restore to another database?


> 
> I just did the dumps as requested, neither of them are showing the index create as expected.

As requested being?:

For table w/data:


pg_dump -d some_db -U some_user -t name_hidden.bcf_work_type -f
bcf_work_type.sql


with table schema only:


pg_dump -d some_db -U some_user -s -t name_hidden.bcf_work_type -f
bcf_work_type.sql


This will produce a plain text SQL script.


To restore:


psql -d some_other_db -U some_user -f bcf_work_type.sql


Was this with the index in the originating database being in a 
functional state?

As a general note you need to provide more supporting information when 
replying. This thread has gone through so many iterations of conditions 
it helps to know the exact conditions you are currently working under.


-- 
Adrian Klaver
adrian.klaver@aklaver.com