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

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails
Дата
Msg-id 20190404013510.GB7693@paquier.xyz
обсуждение исходный текст
Ответ на BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails  (PG Bug reporting form <noreply@postgresql.org>)
Ответы Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Список 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
Вложения

В списке pgsql-bugs по дате отправления:

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails
Следующее
От: David Rowley
Дата:
Сообщение: Re: BUG #15383: Join Filter cost estimation problem in 10.5