Re: "ERROR: could not open relation with OID 16391" error was encountered when reindexing

From: feichanghong <feichanghong(at)qq(dot)com>
To: Aleksander Alekseev <aleksander(at)timescale(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: "ERROR: could not open relation with OID 16391" error was encountered when reindexing
Date: 2024-01-16 14:26:52
Message-ID: tencent_9EBF0764BC74FA7CBC9B8873E0206429B50A@qq.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thank you for your attention.

>
> Any chance you could provide minimal steps to reproduce the issue on
> an empty PG instance, ideally as a script? That's going to be helpful
> to reproduce / investigate the issue and also make sure that it's
> fixed.

I have provided a python script in the attachment to minimize the reproduction of the issue.

The specific reproduction steps are as follows:
1. Initialize the data
```
DROP TABLE IF EXISTS tbl_part;
CREATE TABLE tbl_part (a integer) PARTITION BY RANGE (a);
CREATE TABLE tbl_part_p1 PARTITION OF tbl_part FOR VALUES FROM (0) TO (10);
CREATE INDEX ON tbl_part(a);
```
2. session1 reindex and gdb break at index.c:3585
```
REINDEX INDEX tbl_part_a_idx;
```
3. session2 drop index succeed

```
DROP INDEX tbl_part_a_idx;
```
4. session1 gdb continue


Best Regards,
Fei Changhong
Alibaba Cloud Computing Ltd.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Verite 2024-01-16 14:42:45 Re: Fixing backslash dot for COPY FROM...CSV
Previous Message Nathan Bossart 2024-01-16 14:20:19 Re: reorganize "Shared Memory and LWLocks" section of docs