Re: pgsql: Correct replication origin's use of UINT16_MAX to PG_UINT16_MAX. - Mailing list pgsql-committers

From Alvaro Herrera
Subject Re: pgsql: Correct replication origin's use of UINT16_MAX to PG_UINT16_MAX.
Date
Msg-id 20150430022234.GM4369@alvh.no-ip.org
Whole thread Raw
In response to pgsql: Correct replication origin's use of UINT16_MAX to PG_UINT16_MAX.  (Andres Freund <andres@anarazel.de>)
List pgsql-committers
Andres Freund wrote:
> Correct replication origin's use of UINT16_MAX to PG_UINT16_MAX.
>
> We can't rely on UINT16_MAX being present, which is why we introduced
> PG_UINT16_MAX...
>
> Buildfarm animal bowerbird via Andrew Gierth.

You mixed up your Andrews!

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


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Fix parallel make risk with new check temp-install setup
Next
From: Michael Paquier
Date:
Subject: Re: pgsql: Introduce replication progress tracking infrastructure.