From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Wim Rouquart <wim(dot)rouquart(at)kbc(dot)be>, Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Index (primary key) corrupt? |
Date: | 2025-09-20 20:16:40 |
Message-ID: | 795E8AB6-CE90-4BEE-B410-BD2B15E9DC92@gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On Sep 20, 2025, at 9:58 AM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> On 9/20/25 09:26, Rob Sargent wrote:
>>> So the problem goes away once you’ve reindexed yet you claim it’s consistent? What are you doing to get the problem to recur after you’ve done reindex to make it work?
>>> David
>> I was assuming the OP has a dump of the affected condition and is restoring (and perhaps re-fixing). No?
>
> From this post:
>
> https://www.postgresql.org/message-id/AS2PR05MB107548567EEDAAB3AF74A6C59EF11A%40AS2PR05MB10754.eurprd05.prod.outlook.com
>
> "
> > 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.
> "
>
> Make of that what you will.
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
I don’t see the complete REINDEX command used but from the output of the query on pg_index it looks like reindex using index name would succeed, no? Again assuming this was done against the dump which may or may not have matched a grep attempt. Lord knows I’ve had my share of false negatives with grep.
From | Date | Subject | |
---|---|---|---|
Previous Message | Adrian Klaver | 2025-09-20 16:58:02 | Re: Index (primary key) corrupt? |