Re: Patch for nodeIncrementalSort comment correction.

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: James Coleman <jtc331(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Patch for nodeIncrementalSort comment correction.
Date: 2020-07-20 01:46:08
Message-ID: CAA4eK1+Xtjz-7eTE9TXwLHUzJdzRxeT0mRBUyF1k-GhpejNrmw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jul 19, 2020 at 7:25 PM James Coleman <jtc331(at)gmail(dot)com> wrote:
>
> On Saturday, July 18, 2020, vignesh C <vignesh21(at)gmail(dot)com> wrote:
>>
>> Hi,
>>
>> One of the comments needs correction "sorting all tuples in the the
>> dataset" should have been "sorting all tuples in the dataset".
>> The Attached patch has the changes for the same.
>>
>
>
> Thanks for fixing this. Looks correct to me.
>

Yeah, looks like a typo will push in some time.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-07-20 02:57:39 Re: Is it useful to record whether plans are generic or custom?
Previous Message Greg Nancarrow 2020-07-20 01:15:02 Re: Libpq support to connect to standby server as priority