Re: Index (primary key) corrupt?

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Wim Rouquart <wim(dot)rouquart(at)kbc(dot)be>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Index (primary key) corrupt?
Date: 2025-09-19 13:04:04
Message-ID: f3ea70b8-c822-4b0f-b564-5e73d34188d4@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 9/19/25 02:40, Wim Rouquart wrote:
> Internal
>
>>> Internal
>>>
>>>
>>> Hello,
>>>
>>> When doing a pg_dump of one of our databases one of the tables primary
>>> keys doesn’t get exported. Pg_dump just skips this index, without any
>>> warning whatsoever (verbose mode was used to doublecheck).
>
>> What is the complete table definition?
>
> CREATE TABLE bcf_work_type (
> id bigserial NOT NULL,
> aml_score int8 NOT NULL,
> CONSTRAINT idx_376814_primary PRIMARY KEY (id)
> );

The table was defined in one step using the above definition?

Or was the the PK added later?

What is the result for the query?:

select * from pg_index where indexrelid = 'idx_376814_primary'::regclass;

How is the table populated with data?

>
>> What is the complete pg_dump command being given?
>
> pg_dump --verbose -p <xxx> -U <xxx> -d <xxx> > dumpverbose.sql 2> dumpverbose.log
>
>> Is the PK definition in the pg_dump file? For plain text format can you grep/find it?
>
> It is in neither, that’s why I'm sure it doesn't get exported. After a REINDEX statement it is.
>
>> How is the dump file being restored?
>
> As the code to generate the index is not in the dumpfile this seems irrelevant to me.
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Wim Rouquart 2025-09-19 13:23:08 RE: Index (primary key) corrupt?
Previous Message Daniel Gustafsson 2025-09-19 10:44:41 Re: Client/server certificates verification support on Android platform