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

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.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/e0f26fc76532defd06caf79d711fa99cea83c532

Modified Files
--------------
src/backend/replication/logical/origin.c |    2 +-
src/include/replication/origin.h         |    2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

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