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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: petr(dot)fedorov(at)phystech(dot)edu, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails
Date: 2019-04-04 01:35:10
Message-ID: 20190404013510.GB7693@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2019-04-04 04:37:03 Re: BUG #15383: Join Filter cost estimation problem in 10.5
Previous Message PG Bug reporting form 2019-04-03 18:22:34 BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails