mirror of
https://github.com/postgres/postgres.git
synced 2026-03-03 05:40:43 -05:00
b0a55e4329
We have been using the term RelFileNode to refer to either (1) the integer that is used to name the sequence of files for a certain relation within the directory set aside for that tablespace/database combination; or (2) that value plus the OIDs of the tablespace and database; or occasionally (3) the whole series of files created for a relation based on those values. Using the same name for more than one thing is confusing. Replace RelFileNode with RelFileNumber when we're talking about just the single number, i.e. (1) from above, and with RelFileLocator when we're talking about all the things that are needed to locate a relation's files on disk, i.e. (2) from above. In the places where we refer to (3) as a relfilenode, instead refer to "relation storage". Since there is a ton of SQL code in the world that knows about pg_class.relfilenode, don't change the name of that column, or of other SQL-facing things that derive their name from it. On the other hand, do adjust closely-related internal terminology. For example, the structure member names dbNode and spcNode appear to be derived from the fact that the structure itself was called RelFileNode, so change those to dbOid and spcOid. Likewise, various variables with names like rnode and relnode get renamed appropriately, according to how they're being used in context. Hopefully, this is clearer than before. It is also preparation for future patches that intend to widen the relfilenumber fields from its current width of 32 bits. Variables that store a relfilenumber are now declared as type RelFileNumber rather than type Oid; right now, these are the same, but that can now more easily be changed. Dilip Kumar, per an idea from me. Reviewed also by Andres Freund. I fixed some whitespace issues, changed a couple of words in a comment, and made one other minor correction. Discussion: http://postgr.es/m/CA+TgmoamOtXbVAQf9hWFzonUo6bhhjS6toZQd7HZ-pmojtAmag@mail.gmail.com Discussion: http://postgr.es/m/CA+Tgmobp7+7kmi4gkq7Y+4AM9fTvL+O1oQ4-5gFTT+6Ng-dQ=g@mail.gmail.com Discussion: http://postgr.es/m/CAFiTN-vTe79M8uDH1yprOU64MNFE+R3ODRuA+JWf27JbhY4hJw@mail.gmail.com |
||
|---|---|---|
| .. | ||
| unicode | ||
| .gitignore | ||
| archive.c | ||
| base64.c | ||
| checksum_helper.c | ||
| compression.c | ||
| config_info.c | ||
| controldata_utils.c | ||
| cryptohash.c | ||
| cryptohash_openssl.c | ||
| d2s.c | ||
| d2s_full_table.h | ||
| d2s_intrinsics.h | ||
| digit_table.h | ||
| encnames.c | ||
| exec.c | ||
| f2s.c | ||
| fe_memutils.c | ||
| file_perm.c | ||
| file_utils.c | ||
| hashfn.c | ||
| hmac.c | ||
| hmac_openssl.c | ||
| ip.c | ||
| jsonapi.c | ||
| keywords.c | ||
| kwlookup.c | ||
| link-canary.c | ||
| logging.c | ||
| Makefile | ||
| md5.c | ||
| md5_common.c | ||
| md5_int.h | ||
| pg_get_line.c | ||
| pg_lzcompress.c | ||
| pg_prng.c | ||
| pgfnames.c | ||
| protocol_openssl.c | ||
| psprintf.c | ||
| relpath.c | ||
| restricted_token.c | ||
| rmtree.c | ||
| ryu_common.h | ||
| saslprep.c | ||
| scram-common.c | ||
| sha1.c | ||
| sha1_int.h | ||
| sha2.c | ||
| sha2_int.h | ||
| sprompt.c | ||
| string.c | ||
| stringinfo.c | ||
| unicode_norm.c | ||
| username.c | ||
| wait_error.c | ||
| wchar.c | ||