| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Rob Sargent <robjsargent(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | 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 16:58:02 |
| Message-ID: | 92999289-f47b-46ac-8867-9fa08041e2ac@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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:
"
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Sargent | 2025-09-20 20:16:40 | Re: Index (primary key) corrupt? |
| Previous Message | Rob Sargent | 2025-09-20 16:26:55 | Re: Index (primary key) corrupt? |