pgsql: Use int64 instead of long in incremental sort code

From: David Rowley <drowley(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Use int64 instead of long in incremental sort code
Date: 2020-08-02 02:25:07
Message-ID: E1k23gR-0001Bh-0K@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Use int64 instead of long in incremental sort code

Windows 64bit has 4-byte long values which is not suitable for tracking
disk space usage in the incremental sort code. Let's just make all these
fields int64s.

Author: James Coleman
Discussion: https://postgr.es/m/CAApHDvpky%2BUhof8mryPf5i%3D6e6fib2dxHqBrhp0Qhu0NeBhLJw%40mail.gmail.com
Backpatch-through: 13, where the incremental sort code was added

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/6ee3b5fb990ea11992b0db960d79b1fbe7b5e8e5

Modified Files
--------------
src/backend/commands/explain.c | 20 ++++++++++----------
src/include/nodes/execnodes.h | 8 ++++----
src/include/utils/tuplesort.h | 2 +-
3 files changed, 15 insertions(+), 15 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Etsuro Fujita 2020-08-02 03:01:51 Re: pgsql: Fix some issues with step generation in partition pruning.
Previous Message David Rowley 2020-08-02 02:24:35 pgsql: Use int64 instead of long in incremental sort code