Re: pg_upgrade failed with ERROR: null relpartbound for relation 18159 error.
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Michael Paquier <michael@paquier.xyz>, Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2018-10-07T01:15:32Z
Lists: pgsql-hackers
On 2018-Oct-05, Amit Langote wrote: > On 2018/10/05 16:05, Michael Paquier wrote: > >> As of commit 2fbdf1b38bc [1], which has been applied in 11 and HEAD > >> branches, RelationBuildPartitionDesc emits an error if we don't find > >> relpartbound set for a child found by scanning pg_inherits, instead of > >> skipping such children. While that commit switched the order of creating > >> pg_inherits entry and checking a new bound against existing bounds in > >> DefineRelation in light of aforementioned change, it didn't in > >> ATExecAttachPartition, hence this error. > >> > >> Attached patch fixes that. > > > > Could you please add a minimal regression test in your patch? That's > > the second bug related to ATTACH PARTITION I am looking at today.. > > OK, done, although I hope that's not bloating the tests. Pushed to 11 and master. I'm not convinced that it's a good idea to mess with 10 at this point -- the partitioning code is rather completely different already ... -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Add regression test for ATTACH PARTITION
- afe9b9e68afb 10.6 landed
-
Fix catalog insertion order for ATTACH PARTITION
- 39808e8868c8 12.0 landed
- 1c7f585b5c1a 11.0 landed
-
Simplify partitioned table creation vs. relcache
- 2fbdf1b38bc5 12.0 cited