| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | fedor_erastov(at)mail(dot)ru, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: BUG #16644: null value for defaults in OLD variable for trigger |
| Date: | 2020-10-26 03:19:04 |
| Message-ID: | 638928.1603682344@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Amit Langote <amitlangote09(at)gmail(dot)com> writes:
> On Mon, Oct 26, 2020 at 5:53 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Moreover, it's more correct, even disregarding the problem
>> at hand, because the tlist isn't a perfectly accurate depiction of
>> the relation rowtype: ExecCleanTypeFromTL will not derive the correct
>> info for dropped columns.
> Hmm, I don't understand. Isn't it the planner's job to make the
> targetlist correctly account for dropped columns; what
> expand_targetlist() does?
Yes, there are columns in the tlist to match them, but ExecCleanTypeFromTL
cannot mark those columns as "attisdropped". The column data type
likely won't be right either. The latter shouldn't matter, if the
column is being filled with a null ... but I'm a bit surprised that
we've gotten away this long with not being honest about attisdropped.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2020-10-26 08:51:40 | Re: BUG #16644: null value for defaults in OLD variable for trigger |
| Previous Message | Amit Langote | 2020-10-26 03:11:23 | Re: BUG #16644: null value for defaults in OLD variable for trigger |