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

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: petr.fedorov@phystech.edu, pgsql-bugs@lists.postgresql.org
Date: 2019-04-04T01:35:10Z
Lists: pgsql-bugs
On Wed, Apr 03, 2019 at 06:22:34PM +0000, PG Bug reporting form wrote:
> 6. FAIL: Insert the row which would land at partitioned_2_1_1:
> 
> insert into partitioned values(2,2,1, 1,1); 
> 
> ERROR: cannot extract attribute from empty tuple slot SQL state: XX000

Indeed.  I can see that for v11 but not for HEAD.  Let's keep track of
that.  (Not looking at that now though)
--
Michael

Commits

  1. Fix partition tuple routing with dropped attributes

  2. Add more tests for partition tuple routing with dropped attributes