summaryrefslogtreecommitdiff
path: root/src/backend/catalog/partition.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-05-05 13:10:07 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2019-05-05 13:10:07 -0400
commit9691aa72e2a7fb146ac759e1f8a8b04962128cc0 (patch)
tree1a21f675aad53fbb043617a6bcff28c312758013 /src/backend/catalog/partition.c
parent62148c3520b562e518f17134b22120bab0cb113b (diff)
downloadpostgresql-9691aa72e2a7fb146ac759e1f8a8b04962128cc0.tar.gz
Fix style violations in syscache lookups.
Project style is to check the success of SearchSysCacheN and friends by applying HeapTupleIsValid to the result. A tiny minority of calls creatively did it differently. Bring them into line with the rest. This is just cosmetic, since HeapTupleIsValid is indeed just a null check at the moment ... but that may not be true forever, and in any case it puts a mental burden on readers who may wonder why these call sites are not like the rest. Back-patch to v11 just to keep the branches in sync. (The bulk of these errors seem to have originated in v11 or v12, though a few are old.) Per searching to see if anyplace else had made the same error repaired in 62148c352.
Diffstat (limited to 'src/backend/catalog/partition.c')
-rw-r--r--src/backend/catalog/partition.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/catalog/partition.c b/src/backend/catalog/partition.c
index 8ea7a62418..da98c54391 100644
--- a/src/backend/catalog/partition.c
+++ b/src/backend/catalog/partition.c
@@ -164,7 +164,7 @@ index_get_partition(Relation partition, Oid indexId)
bool ispartition;
tup = SearchSysCache1(RELOID, ObjectIdGetDatum(partIdx));
- if (!tup)
+ if (!HeapTupleIsValid(tup))
elog(ERROR, "cache lookup failed for relation %u", partIdx);
classForm = (Form_pg_class) GETSTRUCT(tup);
ispartition = classForm->relispartition;