diff options
author | Heikki Linnakangas | 2023-12-08 07:47:15 +0000 |
---|---|---|
committer | Heikki Linnakangas | 2023-12-08 07:47:15 +0000 |
commit | b31ba5310b5176402b60abc0454a033b1210ab75 (patch) | |
tree | 664161b9838a21c86e2402dc48f73d1336936270 /src/backend/postmaster/autovacuum.c | |
parent | 15916ffb0468d0b1036ba661767fe6e1b5fb3ee8 (diff) |
Rename ShmemVariableCache to TransamVariables
The old name was misleading: It's not a cache, the values kept in the
struct are the authoritative source.
Reviewed-by: Tristan Partin, Richard Guo
Discussion: https://www.postgresql.org/message-id/[email protected]
Diffstat (limited to 'src/backend/postmaster/autovacuum.c')
-rw-r--r-- | src/backend/postmaster/autovacuum.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/postmaster/autovacuum.c b/src/backend/postmaster/autovacuum.c index 3e037248d61..b04fcfc8c8d 100644 --- a/src/backend/postmaster/autovacuum.c +++ b/src/backend/postmaster/autovacuum.c @@ -2640,8 +2640,8 @@ deleted: * * Even if we didn't vacuum anything, it may still be important to do * this, because one indirect effect of vac_update_datfrozenxid() is to - * update ShmemVariableCache->xidVacLimit. That might need to be done - * even if we haven't vacuumed anything, because relations with older + * update TransamVariables->xidVacLimit. That might need to be done even + * if we haven't vacuumed anything, because relations with older * relfrozenxid values or other databases with older datfrozenxid values * might have been dropped, allowing xidVacLimit to advance. * |