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

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Correct replication origin's use of UINT16_MAX to PG_UINT16_MAX.
Date: 2015-04-29 22:22:59
Message-ID: E1YnaNf-0002dI-2H@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2015-04-29 22:26:34 Re: pgsql: Introduce replication progress tracking infrastructure.
Previous Message Robert Haas 2015-04-29 22:06:43 pgsql: Add <literal> markup, for consistency.