Re: "long" type is not appropriate for counting tuples

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org,Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>,PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "long" type is not appropriate for counting tuples
Date: 2019-05-22 15:26:14
Message-ID: 671B8737-F044-41FF-A2F2-B72615E2245E@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On May 22, 2019 7:39:41 AM PDT, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>On 2019-04-29 19:32, Tom Lane wrote:
>> Another problem is that while "%lu" format specifiers are portable,
>> INT64_FORMAT is a *big* pain, not least because you can't put it into
>> translatable strings without causing problems. To the extent that
>> we could go over to "%zu" instead, maybe this could be finessed,
>> but blind "s/long/int64/g" isn't going to be any fun.
>
>Since we control our own snprintf now, this could probably be addressed
>somehow, right?

z is for size_t though? Not immediately first how It'd help us?

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleksii Kliukin 2019-05-22 15:27:15 upgrades in row-level locks can deadlock
Previous Message Bruce Momjian 2019-05-22 15:21:21 Re: PG 12 draft release notes