On 10/10/25 05:28, Wim Rouquart wrote:
> Internal
>
> Hi,
>
> Apologies for the late response, had other fish to fry...
>
> In response to your questions:
>
>> What is full(15.x) version of Postgres are you using?
>
> 15.14
>
>> Is it the community version or a fork or SaaS?
>
> Standard release indeed, running on RHAT8
>
>> What do you get for queries below?:
>
>> select * from pg_opclass where oid = 3124;
>
> |oid |opcmethod |opcname |opcnamespace|opcowner |opcfamily |opcintype |opcdefault
|opckeytype
> |3124 |403 |int8_ops |11 |10 |1976 |20
|true |0
>
>> select * from pg_opclass where opcname = 'int8_ops';
>
> |oid |opcmethod |opcname |opcnamespace |opcowner |opcfamily |opcintype |opcdefault
|opckeytype|
> |3124 |403 |int8_ops |11 |10 |1976 |20
|true |0 |
> |10021 |405 |int8_ops |11 |10 |1977 |20
|true |0 |
>
Was the above done before or after you did the reindex?
From original post:
"
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).
When doing a REINDEX the issue is fixed.
"
That would imply that after the successful REINDEX and dump some action
is taken that makes the index disappear.
What is the table used for?
Are there any sort of 'unusual' operations done on it?
--
Adrian Klaver
adrian.klaver@aklaver.com
