Re: default partition and concurrent attach partition
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Amit Langote <amitlangote09@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>, Robert Haas <robertmhaas@gmail.com>, hawu@vmware.com
Date: 2020-09-07T22:10:07Z
Lists: pgsql-hackers
On 2020-Sep-07, Alvaro Herrera wrote: > Well, they are fake in that the ri_RangeTableIndex they carry is bogus, > which means that ExecBuildSlotValueDescription will misbehave if the > partitioned default partition has a different column order than its > parent. That can be evidenced by changing the setup block in the > isolation test as in the attached; and you'll get an undesirable error > like this: > > 2020-09-07 19:00:49.513 -03 [12981] ERROR: attribute 2 of type record has wrong type > 2020-09-07 19:00:49.513 -03 [12981] DETAIL: Table has type text, but query expects integer. > 2020-09-07 19:00:49.513 -03 [12981] STATEMENT: insert into attach_tab values (110, 'eleven and five twenties'); ... and I sent before completing. I'm not sure what a good fix for this is. We could try to initialize the resultRelInfo honestly, or we could set ri_RangeTableIndex to some invalid value that will ... eh ... do something else. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Check default partitions constraints while descending
- f481d2823297 14.0 landed
- ef1e1250e716 12.5 landed
- d0230a43fcae 13.0 landed