Re: Missing SIZE_MAX

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2017-09-01T16:35:51Z

Lists: pgsql-hackers

On Fri, Sep 1, 2017 at 12:22 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> [ warning: more than you really wanted to know ahead ]

It might be worth the effort to clean all of this up, just because the
next person who gets bitten by it may not be as smart as you are.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

Make [U]INT64CONST safe for use in #if conditions.
- 9d6b160d7db7 11.0 landed
- f60a236bab80 9.2.24 landed
- f2fe1cbef11c 10.0 landed
- dd344de6718b 9.3.20 landed
- 53863ebeba5f 9.4.15 landed
- 3a0f8e7d3f9a 9.6.6 landed
- 1305186de425 9.5.10 landed
Ensure SIZE_MAX can be used throughout our code.
- bf387028554f 9.5.10 landed
- 9a98557662a9 9.4.15 landed
- 0bfcda990405 9.2.24 landed
- 074985b26a43 9.3.20 landed
- e50d401a8396 9.6.6 landed
- cbb51eb69f3f 10.0 landed
- b79d69b08756 11.0 landed
Teach libpq to detect integer overflow in the row count of a PGresult.
- 2e70d6b5e99b 11.0 cited