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.
This commit is contained in:
Andres Freund 2015-04-30 00:19:36 +02:00
parent 49601ab1a6
commit e0f26fc765
2 changed files with 2 additions and 2 deletions

View File

@ -266,7 +266,7 @@ replorigin_create(char *roname)
rel = heap_open(ReplicationOriginRelationId, ExclusiveLock);
for (roident = InvalidOid + 1; roident < UINT16_MAX; roident++)
for (roident = InvalidOid + 1; roident < PG_UINT16_MAX; roident++)
{
bool nulls[Natts_pg_replication_origin];
Datum values[Natts_pg_replication_origin];

View File

@ -30,7 +30,7 @@ typedef struct xl_replorigin_drop
#define XLOG_REPLORIGIN_DROP 0x10
#define InvalidRepOriginId 0
#define DoNotReplicateId UINT16_MAX
#define DoNotReplicateId PG_UINT16_MAX
extern PGDLLIMPORT RepOriginId replorigin_sesssion_origin;
extern PGDLLIMPORT XLogRecPtr replorigin_sesssion_origin_lsn;