mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Ensure pg_filenode_relation(0, 0) returns NULL.

Browse Source 
Previously, a zero value for the relfilenode resulted in
a confusing error message about "unexpected duplicate".
This function returns NULL for other invalid relfilenode
values, so zero should be treated likewise.

It's been like this all along, so back-patch to all supported
branches.

Justin Pryzby

Discussion: https://postgr.es/m/20210612023324.GT16435@telsasoft.com
This commit is contained in:
Tom Lane 2021-06-12 13:29:24 -04:00
parent 8b5055812c
commit f479ea94bd
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/backend/utils/adt/dbsize.c
View File

@ -921,7 +921,11 @@ pg_filenode_relation(PG_FUNCTION_ARGS)
{ {
Oid reltablespace = PG_GETARG_OID(0); Oid reltablespace = PG_GETARG_OID(0);
Oid relfilenode = PG_GETARG_OID(1); Oid relfilenode = PG_GETARG_OID(1);
Oid heaprel = InvalidOid; Oid heaprel;
/* test needed so RelidByRelfilenode doesn't misbehave */
if (!OidIsValid(relfilenode))
PG_RETURN_NULL();
heaprel = RelidByRelfilenode(reltablespace, relfilenode); heaprel = RelidByRelfilenode(reltablespace, relfilenode);