Re: BUG #16242: convert_tuple_* not handling missing values correctly - Mailing list pgsql-bugs

From Vik Fearing
Subject Re: BUG #16242: convert_tuple_* not handling missing values correctly
Date
Msg-id 3c396c9e-960f-9c03-63b7-d58e0e044fba@postgresfriends.org
Whole thread Raw
In response to Re: BUG #16242: convert_tuple_* not handling missing values correctly  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #16242: convert_tuple_* not handling missing values correctly
List pgsql-bugs
On 05/02/2020 03:19, Andres Freund wrote:
> On 2020-02-05 03:03:04 +0100, Vik Fearing wrote:
>> On 04/02/2020 03:24, PG Bug reporting form wrote:
>>> The following example shows a tuple appearing with NULLs in a column
>>> declared NOT NULL, because there is a missing default value not being filled
>>> in. The cause is that convert_tuples_by_name, or more precisely
>>> check_attrmap_match, thinks that it's enough for the tupdescs to match up as
>>> regards attnums/names/types, without considering that the source tupdesc
>>> might have missing values that the destination does not. So it incorrectly
>>> concludes that no conversion is needed, and the missing values become
>>> null.
>>
>> Here is a quick patch that fixes this on master.
> 
> Should include a regression test...

That's what I thought, too.  Where should I put it?
-- 
Vik Fearing



pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #16242: convert_tuple_* not handling missing values correctly
Next
From: Andres Freund
Date:
Subject: Re: BUG #16242: convert_tuple_* not handling missing values correctly