Internal
I already saw finding the actual cause as a 'lost cause' as these things tend to happen, however what bothers me most
isthat a tool like amcheck which is supposed to find corruption also shows up with no result.
-----Original Message-----
From: Adrian Klaver <adrian.klaver@aklaver.com>
Sent: vrijdag 6 maart 2026 17:03
To: Wim Rouquart <wim.rouquart@kbc.be>; Greg Sabino Mullane <htamfids@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Index (primary key) corrupt?
The real sender of this external email is adrian.klaver@aklaver.com
On 3/6/26 2:31 AM, Wim Rouquart wrote:
> Internal
>
>
>> As I recall this is not a large table, but for completeness what is it's average size?
>
> It has only 12 rows 😊
>
>> What are the Postgres log settings, on the source database, for?:
>
> log_error_verbosity = 'default'
> log_min_error_statement = 'fatal'
> log_min_messages = 'warning'
> log_statement = 'ddl'
>
>> Are there any entries in the Postgres log that reference this table?
>
> Nope, none found, probably because it isn't used anymore (and because
> of above log settings if it would be)
>
Well at this point I don't see that it is possible to determine a cause for why the index does not transfer or throw an
errorin the process.
--
Adrian Klaver
adrian.klaver@aklaver.com
Disclaimer <https://www.kbc.com/KBCmailDisclaimer>
