Re: Skip partition tuple routing with constant partition key

From: Zhihong Yu <zyu(at)yugabyte(dot)com>
To: "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>
Subject: Re: Skip partition tuple routing with constant partition key
Date: 2021-05-26 17:35:00
Message-ID: CALNJ-vQ5n=N-Jk0auA9eReF-K7St+Cf6X2x=42Bh001BR0sbCQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> Hi, Amit:
>

For ConvertTupleToPartition() in
0001-ExecFindPartition-cache-last-used-partition-v3.patch:

+ if (tempslot != NULL)
+ ExecClearTuple(tempslot);

If tempslot and parent_slot point to the same slot, should ExecClearTuple()
still be called ?

Cheers

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2021-05-26 17:56:38 Re: storing an explicit nonce
Previous Message Tom Lane 2021-05-26 17:28:07 Re: CALL versus procedures with output-only arguments