GetNextNodeId() incorrectly called PG_RETURN_DATUM

- Also stabilize the output of a multi_router_planner test
release-7.1
Brian Cloutier 2018-01-29 15:32:36 -08:00 committed by Jason Petersen
parent 73e786b0c6
commit d9cf5ff3ab
5 changed files with 11 additions and 9 deletions

View File

@ -1192,20 +1192,18 @@ GetNextNodeId()
Datum sequenceIdDatum = ObjectIdGetDatum(sequenceId);
Oid savedUserId = InvalidOid;
int savedSecurityContext = 0;
Datum nextNodedIdDatum = 0;
Datum nextNodeIdDatum;
int nextNodeId = 0;
GetUserIdAndSecContext(&savedUserId, &savedSecurityContext);
SetUserIdAndSecContext(CitusExtensionOwner(), SECURITY_LOCAL_USERID_CHANGE);
/* generate new and unique shardId from sequence */
nextNodedIdDatum = DirectFunctionCall1(nextval_oid, sequenceIdDatum);
nextNodeIdDatum = DirectFunctionCall1(nextval_oid, sequenceIdDatum);
SetUserIdAndSecContext(savedUserId, savedSecurityContext);
PG_RETURN_DATUM(nextNodedIdDatum);
nextNodeId = DatumGetUInt32(nextNodeId);
nextNodeId = DatumGetUInt32(nextNodeIdDatum);
return nextNodeId;
}

View File

@ -1153,7 +1153,8 @@ SELECT
FROM
articles_hash_mx
GROUP BY
author_id;
author_id
ORDER BY c;
c
---
4

View File

@ -1832,7 +1832,8 @@ SELECT
FROM
articles_hash
GROUP BY
author_id;
author_id
ORDER BY c;
c
---
4

View File

@ -530,7 +530,8 @@ SELECT
FROM
articles_hash_mx
GROUP BY
author_id;
author_id
ORDER BY c;
-- queries inside transactions can be router plannable
BEGIN;

View File

@ -900,7 +900,8 @@ SELECT
FROM
articles_hash
GROUP BY
author_id;
author_id
ORDER BY c;
-- queries inside transactions can be router plannable
BEGIN;