From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: minor fix for acquire_inherited_sample_rows |
Date: | 2018-04-23 13:15:47 |
Message-ID: | CA+HiwqG=gcv3g+FjXsXmeYZCvcVgYaJ0u+A9wW4FtYVKw+44Ew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thanks for the review.
On Mon, Apr 23, 2018 at 8:25 PM, Ashutosh Bapat
<ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> On Mon, Apr 23, 2018 at 3:44 PM, Amit Langote
> <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> Hi.
>>
>> acquire_inherited_sample_rows() currently uses equalTupleDescs() being
>> false as the condition for going to tupconv.c to determine whether tuple
>> conversion is needed. But equalTupleDescs() will always return false if
>> it's passed TupleDesc's of two different tables, which is the most common
>> case here. So I first thought we should just unconditionally go to
>> tupconv.c, but there is still one case where we don't need to, which is
>> the case where the child table is same as the parent table. However, it
>> would be much cheaper to just check if the relation OIDs are different
>> instead of calling equalTupleDescs, which the attached patch teaches it to do.
>
> We want to check whether tuple conversion is needed. Theoretically
> (not necessarily practically), one could have tuple descs of two
> different tables stamped with the same tdtypeid. From that POV,
> equalTupleDescs seems to be a stronger check than what you have in the
> patch.
If I'm reading right, that sounds like a +1 to the patch. :)
> BTW the patch you have posted also has a fix you proposed in some
> other thread. Probably you want to get rid of it.
Oops, fixed that in the attached.
Thanks,
Amit
Attachment | Content-Type | Size |
---|---|---|
condition-may-need-tuple-conversion.patch | application/octet-stream | 554 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Darafei Komяpa Praliaskouski | 2018-04-23 14:32:49 | Re: psql leaks memory on query cancellation |
Previous Message | Teodor Sigaev | 2018-04-23 12:57:34 | Re: Corrupted btree index on HEAD because of covering indexes |