Re: pgsql: Correct replication origin's use of UINT16_MAX to PG_UINT16_MAX.

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Correct replication origin's use of UINT16_MAX to PG_UINT16_MAX.
Date: 2015-04-30 02:22:35
Message-ID: 20150430022234.GM4369@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2015-04-30 02:52:45 Re: pg_upgrade: quote directory names in delete_old_cluster script
Previous Message Peter Eisentraut 2015-04-30 00:54:47 pgsql: Fix parallel make risk with new check temp-install setup