like this:
REINDEX INDEX idx_376814_primary;
the export import story works just fine, the index is in there and is created.
Cheers,
Wim.
On Sat, Sep 20, 2025 at 5:07 AM Wim Rouquart
mailto:[email protected]>> wrote:
Name |Value |
---+---
s, until I do the rebuild and then the issue is fixed.
On 9/19/25 06:23, Wim Rouquart wrote:
>> What is the result for the query?:
>
>> select * from pg_index where indexrelid =
>> 'idx_376814_primary'::regclass;
>
> Name |Value |
&
Internal
Yes indeed, i just restore the database to before the rebuild.
> 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 o
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
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?
>>
>> CREAT
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).
When doing a REINDEX the issue is fixed.
As this seems to me to be some form
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).
When doing a REINDEX the issue is fixed.
As this seems to me to be some form
