Postgres Pro
Downloads
Home   >   mailing lists

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

From Andres Freund
Subject pgsql: Correct replication origin's use of UINT16_MAX to PG_UINT16_MAX.
Date
Msg-id E1YnaNf-0002dI-2H@gemulon.postgresql.org
Whole thread Raw
Responses Re: pgsql: Correct replication origin's use of UINT16_MAX to PG_UINT16_MAX.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-committers
Tree view 
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(-)

pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: Add markup, for consistency.
Next
From: Andres Freund
Date:
Subject: Re: pgsql: Introduce replication progress tracking infrastructure.