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

From Amit Langote
Subject Re: [HACKERS] No-op case in ExecEvalConvertRowtype
Date
Msg-id 9ed07043-ef2d-7b08-7847-3afee2bdeb50@lab.ntt.co.jp
Whole thread Raw
In response to Re: [HACKERS] No-op case in ExecEvalConvertRowtype  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
List pgsql-hackers
On 2017/04/07 12:16, Ashutosh Bapat wrote:
> 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

Sorry I probably wasn't clear.  3f902354b08 is what Tom committed earlier
today.

Thanks,
Amit





pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: [HACKERS] Hash tables in dynamic shared memory
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] Foreign tables don't enforce the partition constraint