On 10/28/25 03:25, Wim Rouquart wrote:
Internal
I used the output from DBeaver, guess it acted up. Here’s the output
from psql:
1) As side note, find a different client to use then DBeaver. I have
seen many Postgres questions on Stack Overflow where the answer was, use
something other then DBeaver.
2) Where and when was the query below run, on the original instance
before the pg_dump or on the new instance after the restore and index
rebuild?
3) From this post:
https://www.postgresql.org/message-id/AS2PR05MB107548567EEDAAB3AF74A6C59EF11A%40AS2PR05MB10754.eurprd05.prod.outlook.com
"
It is in neither, that’s why I'm sure it doesn't get exported. After a
REINDEX statement it is."
From here:
https://www.postgresql.org/docs/current/sql-reindex.html
"REINDEX rebuilds an index using the data stored in the index's table,
replacing the old copy of the index."
The question then is, how does a REINDEX work on an index that
supposedly does not exist?
When you do the original restore and before the REINDEX, in psql, what
does the below return?:
\d bcf_work_type
select * from pg_index where indexrelid = 'idx_376814_primary'::regclass;
-[ RECORD 1 ]-------+--------
indexrelid | 2006873
indrelid | 1998823
indnatts | 1
indnkeyatts | 1
indisunique | t
indnullsnotdistinct | f
indisprimary | t
indisexclusion | f
indimmediate | t
indisclustered | f
indisvalid | t
indcheckxmin | f
indisready | t
indislive | t
indisreplident | f
indkey | 1
indcollation | 0
indclass | 3124
indoption | 0
indexprs |
indpred |
The steps that show the index is missing is an export of the database
while the index is ‘corrupt’, and then importing it. The import fails on
foreign keys that are pointing to this index because it is indeed not
created.
Checking the export file shows the create statement from the index is
indeed missing (I know it can show up lower in the file, a search was
done on the index name, it’s not in there, you’re going to have to trust
me on this).
After doing a reindex 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 <[email protected]
<mailto:[email protected]>> wrote:
Name |Value |
-------------------+-------+
indexrelid |2006873|
indrelid |1998823|
indnatts |1 |
indnkeyatts |1 |
...
indclass |{} |
Hold on, that makes no sense at all. The indkey/indclass columns cannot
be empty, especially as indnkeyatts is 1, as it should be. As a matter
of fact, pg_dump would completely choke on a broken table like this and
not even be able to dump it. But that output is clearly not from psql,
so I think whatever client application you are using is not able to
reliably output array columns. Any chance you can run that select
command using psql? As the rest of the columns look sane, I'm going to
guess those are as well, they just don't show up correctly, and the
system catalogs are uncorrupted.
until I do the rebuild and then the issue is fixed
Could you show us exactly the steps that show the index is missing, and
that it is then fixed?
(ponders) Keep in mind that although you declared the primary key in
your create table statement, pg_dump is going to separate the table
creation from the primary key creation by a lot of lines. So you will
see in the pg_dump output:
CREATE TABLE public.bcf_work_type (
id bigint NOT NULL,
aml_score bigint NOT NULL
);
and then much later on:
ALTER TABLE ONLY public.bcf_work_type
ADD CONSTRAINT idx_376814_primary PRIMARY KEY (id);
Also be aware that if you are using the --section argument, the table
will appear in the 'pre-data' section but the primary key will appear in
the 'post-data' section.
Cheers,
Greg
--
Crunchy Data - https://altered.secure4u.kbc.be/https://
www.crunchydata.com <https://altered.secure4u.kbc.be/https:/
www.crunchydata.com>
Enterprise Postgres Software Products & Tech Support
Disclaimer <https://www.kbc.com/KBCmailDisclaimer>
--
Adrian Klaver
[email protected]
