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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
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-08-14 18:17:09
Message-ID: 20190814181709.hv67u3acg5vjqakz@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

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.

- Andres

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-08-14 18:22:20 Re: getting ERROR "relation 16401 has no triggers" with partition foreign key alter
Previous Message Tom Lane 2019-08-14 18:04:27 Re: proposal: make NOTIFY list de-duplication optional