Re: BUG #14985: ExecCopySlotTuple not set "type id" and "type mod" when from minial tuple"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: bucoo(at)sohu(dot)com, pgsql-bugs(at)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org>
Subject: Re: BUG #14985: ExecCopySlotTuple not set "type id" and "type mod" when from minial tuple"
Date: 2017-12-20 15:37:35
Message-ID: 12020.1513784255@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
> The following bug has been logged on the website:

The bug reporting form is not a good way to discuss proposed code changes,
especially when you haven't shown any reason to think there is a bug.
Please instead start a thread on pgsql-hackers explaining why this would
be a good change to make. (Offhand I'd think it would be a waste of
code, because anything going through the minimal-tuple code path is
just about guaranteed to be an anonymous record type anyway.)

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-12-20 15:39:36 Re: BUG #14984: function "heap_tuple_from_minimal_tuple" lost HeapTupleHeader->t_len value
Previous Message Andres Freund 2017-12-20 15:33:46 Re: BUG #14985: ExecCopySlotTuple not set "type id" and "type mod" when from minial tuple"