RE: Use of "long" in incremental sort code

From: "Tang, Haiying" <tanghy(dot)fnst(at)cn(dot)fujitsu(dot)com>
To: "Tang, Haiying" <tanghy(dot)fnst(at)cn(dot)fujitsu(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, James Coleman <jtc331(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: Use of "long" in incremental sort code
Date: 2020-10-21 06:06:52
Message-ID: 93ab8dbef1df443497ccad78eda68fd0@G08CNEXMBPEKD05.g08.fujitsu.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

>Found one more place needed to be changed(long -> int64).
>
>Also changed the output for int64 data(Debug mode on & define EXEC_SORTDEBUG )
>
>And, maybe there's a typo in " src\backend\executor\nodeIncrementalSort.c" as below.
>Obviously, the ">=" is meaningless, right?
>
>And, maybe there's a typo in " src\backend\executor\nodeIncrementalSort.c" as below.
>Obviously, the ">=" is meaningless, right?
>
>- SO1_printf("Sorting presorted prefix tuplesort with >= %ld tuples\n", nTuples);
>+ SO1_printf("Sorting presorted prefix tuplesort with %ld tuples\n", nTuples);
>
>Please take a check at the attached patch file.

I have added it to commit fest.
https://commitfest.postgresql.org/30/2772/

Best regards
Tang

-----Original Message-----
From: Tang, Haiying <tanghy(dot)fnst(at)cn(dot)fujitsu(dot)com>
Sent: Monday, October 19, 2020 12:57 PM
To: David Rowley <dgrowleyml(at)gmail(dot)com>; James Coleman <jtc331(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: RE: Use of "long" in incremental sort code

Hi

Found one more place needed to be changed(long -> int64).

Also changed the output for int64 data(Debug mode on & define EXEC_SORTDEBUG )

And, maybe there's a typo in " src\backend\executor\nodeIncrementalSort.c" as below.
Obviously, the ">=" is meaningless, right?

- SO1_printf("Sorting presorted prefix tuplesort with >= %ld tuples\n", nTuples);
+ SO1_printf("Sorting presorted prefix tuplesort with %ld tuples\n", nTuples);

Please take a check at the attached patch file.

Previous disscution:
https://www.postgresql.org/message-id/CAApHDvpky%2BUhof8mryPf5i%3D6e6fib2dxHqBrhp0Qhu0NeBhLJw%40mail.gmail.com

Best regards
Tang

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2020-10-21 06:20:22 Re: Error in pg_restore (could not close data file: Success)
Previous Message Kyotaro Horiguchi 2020-10-21 04:45:15 Re: Error in pg_restore (could not close data file: Success)