Fix catalog insertion order for ATTACH PARTITION
Alvaro Herrera <alvherre@alvh.no-ip.org>
Fix catalog insertion order for ATTACH PARTITION Commit 2fbdf1b38bc changed the order in which we inserted catalog rows when creating partitions, so that we could remove an unsightly hack required for untimely relcache invalidations. However, that commit only changed the ordering for CREATE TABLE PARTITION OF, and left ALTER TABLE ATTACH PARTITION unchanged, so the latter can be affected when catalog invalidations occur, for instance when the partition key involves an SQL function. Reported-by: Rajkumar Raghuwanshi Author: Amit Langote Reviewed-by: Michaël Paquier Discussion: https://postgr.es/m/CAKcux6=nTz9KSfTr_6Z2mpzLJ_09JN-rK6=dWic6gGyTSWueyQ@mail.gmail.com
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/commands/tablecmds.c | modified | +3 −3 |
| src/test/regress/expected/alter_table.out | modified | +15 −0 |
| src/test/regress/sql/alter_table.sql | modified | +16 −0 |
Discussion
- pg_upgrade failed with ERROR: null relpartbound for relation 18159 error. 10 messages · 2018-10-03 → 2018-10-09