Commit 937e4e50 authored by Andres Freund's avatar Andres Freund

Fix sepgsql compile error caused by oid removal.

Per buildfarm animal rhinoceros. I (Andres) missed replacing a few
uses of ObjectIdAttributeNumber in sepgsql.

It's quite probable that the sepgsql test output will need more
adapting than done in 578b22...

Author: Thomas Munro
Discussion: https://postgr.es/m/CAEepm=2Sk+66HJV8FLDfm_sKTn22j7cWTY_Y1Rok3RxeWL_Y0w@mail.gmail.com
parent 578b2297
......@@ -80,7 +80,7 @@ sepgsql_database_post_create(Oid databaseId, const char *dtemplate)
rel = heap_open(DatabaseRelationId, AccessShareLock);
ScanKeyInit(&skey,
ObjectIdAttributeNumber,
Anum_pg_database_oid,
BTEqualStrategyNumber, F_OIDEQ,
ObjectIdGetDatum(databaseId));
......
......@@ -59,7 +59,7 @@ sepgsql_proc_post_create(Oid functionId)
rel = heap_open(ProcedureRelationId, AccessShareLock);
ScanKeyInit(&skey,
ObjectIdAttributeNumber,
Anum_pg_proc_oid,
BTEqualStrategyNumber, F_OIDEQ,
ObjectIdGetDatum(functionId));
......@@ -253,7 +253,7 @@ sepgsql_proc_setattr(Oid functionId)
rel = heap_open(ProcedureRelationId, AccessShareLock);
ScanKeyInit(&skey,
ObjectIdAttributeNumber,
Anum_pg_proc_oid,
BTEqualStrategyNumber, F_OIDEQ,
ObjectIdGetDatum(functionId));
......
......@@ -262,7 +262,7 @@ sepgsql_relation_post_create(Oid relOid)
rel = heap_open(RelationRelationId, AccessShareLock);
ScanKeyInit(&skey,
ObjectIdAttributeNumber,
Anum_pg_class_oid,
BTEqualStrategyNumber, F_OIDEQ,
ObjectIdGetDatum(relOid));
......@@ -614,7 +614,7 @@ sepgsql_relation_setattr(Oid relOid)
rel = heap_open(RelationRelationId, AccessShareLock);
ScanKeyInit(&skey,
ObjectIdAttributeNumber,
Anum_pg_class_oid,
BTEqualStrategyNumber, F_OIDEQ,
ObjectIdGetDatum(relOid));
......
......@@ -59,7 +59,7 @@ sepgsql_schema_post_create(Oid namespaceId)
rel = heap_open(NamespaceRelationId, AccessShareLock);
ScanKeyInit(&skey,
ObjectIdAttributeNumber,
Anum_pg_namespace_oid,
BTEqualStrategyNumber, F_OIDEQ,
ObjectIdGetDatum(namespaceId));
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment