Re: BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails

On 2019/04/05 12:22, Amit Langote wrote:
> On 2019/04/04 19:48, Michael Paquier wrote:
>> Perhaps it would make sense to have this test case on HEAD as well?
>
> OK, I've divided the patch that adds tests into its own.
>
>> It seems to me that there is little point in having a completely new
>> set of relations to test this issue knowing that multi-level
>> partitioning is already tested in the same file. Why not extending
>> the part close to "more tests for certain multi-level partitioning
>> scenarios" in insert.sql with a mlparted111 or such a thing? This
>> way, we have a three-layer partitioning and the error can be equally
>> triggered.
>
> Done that way.
>
> v2-0001_*, the test patch, can be applied to HEAD and PG 11 branches. Of
> course, one would want to commit 0001 and 0002 together in PG 11, because
> you'll see the ERROR in the output in patch 0001, which is same as the
> reported error.
>
> I've also modified 0001 so that it can be applied to PG 10, attached as
> pg10-0001*.
>
> Both HEAD and PG 10 don't need any code changes.

I said v2-0001 could be applied unchanged to both HEAD and PG 11, but I
was wrong. Tests without the code changes fail on PG 11, but they pass on
both PG 10 and HEAD as there's no bug in those branches.

Here are revised patches.

pg10-v3-0001 adds tests in PG 10 branch
pg11-v3-0001 adds tests in PG 11 branch t(tests fail which 0002 fixes)
pg11-v3-0002 fixes bug in PG 11 branch
HEAD-v3-0001 adds tests in HEAD branch

I also rewrote tests a bit too, expanding the comment, and finding even
more suitable place in insert.sql to add this test than v2.

Thanks,
Amit