diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2024-08-19 16:09:10 -0400 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2024-08-19 16:09:10 -0400 |
| commit | 3ad4c8615a7616c0d3f6bf6fe9bdd22d43c95813 (patch) | |
| tree | aa6f3165333b78160f33887af8ada8750189ac0d /src/backend/executor/nodeModifyTable.c | |
| parent | 3acbe198e2ad0f7d790d04f87c662ee26738536a (diff) | |
| download | postgresql-3ad4c8615a7616c0d3f6bf6fe9bdd22d43c95813.tar.gz postgresql-3ad4c8615a7616c0d3f6bf6fe9bdd22d43c95813.zip | |
Avoid failure to open dropped detached partition
When a partition is detached and immediately dropped, a prepared
statement could try to compute a new partition descriptor that includes
it. This leads to this kind of error:
ERROR: could not open relation with OID 457639
Avoid this by skipping the partition in expand_partitioned_rtentry if it
doesn't exist.
Noted by me while investigating bug #18559. Kuntal Gosh helped to
identify the exact failure.
Backpatch to 14, where DETACH CONCURRENTLY was introduced.
Author: Álvaro Herrera <alvherre@alvh.no-ip.org>
Reviewed-by: Kuntal Ghosh <kuntalghosh.2007@gmail.com>
Reviewed-by: Junwang Zhao <zhjwpku@gmail.com>
Discussion: https://postgr.es/m/202408122233.bo4adt3vh5bi@alvherre.pgsql
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions