pgsql: Avoid failure to open dropped detached partition - Mailing list pgsql-committers

From Alvaro Herrera
Subject pgsql: Avoid failure to open dropped detached partition
Date
Msg-id E1sg8jk-000SzF-3R@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
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

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/a6ff329e7b7231aba9789922daa25e2367709d50

Modified Files
--------------
src/backend/optimizer/util/inherit.c | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Tomas Vondra
Date:
Subject: pgsql: Document that search_path is reported by the server
Next
From: Bruce Momjian
Date:
Subject: pgsql: doc: Improve vague pg_createsubscriber description