Postgres Pro
Downloads
Home   >   mailing lists

Re: Use of "long" in incremental sort code - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Use of "long" in incremental sort code
Date
Msg-id 864019.1593718782@sss.pgh.pa.us
Whole thread Raw
In response to Re: Use of "long" in incremental sort code  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Use of "long" in incremental sort code  (Peter Geoghegan <pg@bowt.ie>)
Re: Use of "long" in incremental sort code  (James Coleman <jtc331@gmail.com>)
List pgsql-hackers
Tree view 
Peter Geoghegan <pg@bowt.ie> writes:
> On Thu, Jul 2, 2020 at 10:53 AM James Coleman <jtc331@gmail.com> wrote:
>> Do you think it's reasonable to use int64 across the board for memory
>> and disk space numbers then? If so, I can update the patch.

> Using int64 as a replacement for long is the safest general strategy,

mumble ssize_t mumble

            regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_read_file() with virtual files returns empty string
Next
From: Peter Geoghegan
Date:
Subject: Re: Use of "long" in incremental sort code