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

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)bowt(dot)ie>, 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-09-06 12:00:51
Message-ID: a4bd28ef-3eda-86bc-f437-99f3c96765ef@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-08-14 20:17, Andres Freund wrote:
> On 2019-05-22 16:40:28 +0200, Peter Eisentraut wrote:
>> On 2019-04-29 19:52, Andres Freund wrote:
>>> Hm. It appears that gettext supports expanding PRId64 PRIu64 etc in
>>> translated strings.
>>
>> That won't work in non-GNU gettext.
>
> Which of those do we actually support? We already depend on
> bind_textdomain_codeset, which afaict wasn't present in older gettext
> implementations.

At least in theory we support Solaris gettext. In the past we
occasionally got complaints when we broke something there.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2019-09-06 12:10:58 Re: [HACKERS] CLUSTER command progress monitor
Previous Message Surafel Temesgen 2019-09-06 11:52:53 Re: FETCH FIRST clause WITH TIES option