From: | feichanghong <feichanghong(at)qq(dot)com> |
---|---|
To: | feichanghong <feichanghong(at)qq(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com> |
Cc: | pgsql-hackers <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 16:21:11 |
Message-ID: | tencent_0D280DBD476540772E7E689A6471B420000A@qq.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I have provided a python script in the attachment to minimize the reproduction of the issue.
I'm sorry that I lost the attached script in my last reply, but I've added it in this reply.
You can also use psql to reproduce it with the following steps:
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.
Attachment | Content-Type | Size |
---|---|---|
reproduce.py | application/octet-stream | 1.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2024-01-16 16:24:30 | Re: New Window Function: ROW_NUMBER_DESC() OVER() ? |
Previous Message | Nathan Bossart | 2024-01-16 16:07:48 | Re: introduce dynamic shared memory registry |