Re: [HACKERS] No-op case in ExecEvalConvertRowtype - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: [HACKERS] No-op case in ExecEvalConvertRowtype
Date
Msg-id CAFjFpRdqF5ab1Xbb7xdX1MGHsHuuky0cZ4qsYXjb-tRf9Vk3vg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] No-op case in ExecEvalConvertRowtype  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: [HACKERS] No-op case in ExecEvalConvertRowtype  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
On Fri, Apr 7, 2017 at 7:28 AM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:
>
> And I see that just in 3f902354b08 lets the partition tuple-routing code
> keep utilizing that optimization.

I am not able to find this commit
fatal: ambiguous argument '3f902354b08': unknown revision or path not
in the working tree.
Use '--' to separate paths from revisions


-- 
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Faster methods for getting SPI results (460% improvement)
Next
From: Ashutosh Bapat
Date:
Subject: Re: [HACKERS] No-op case in ExecEvalConvertRowtype