From 35d39ba0811b70a439dd5012b0d641843b67b4a9 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sun, 4 Aug 2002 18:12:15 +0000 Subject: [PATCH] Fix obsolete comment. --- src/backend/utils/cache/relcache.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/backend/utils/cache/relcache.c b/src/backend/utils/cache/relcache.c index b95a233bac..f1ed253d71 100644 --- a/src/backend/utils/cache/relcache.c +++ b/src/backend/utils/cache/relcache.c @@ -8,7 +8,7 @@ * * * IDENTIFICATION - * $Header: /cvsroot/pgsql/src/backend/utils/cache/relcache.c,v 1.169 2002/08/02 22:36:05 tgl Exp $ + * $Header: /cvsroot/pgsql/src/backend/utils/cache/relcache.c,v 1.170 2002/08/04 18:12:15 tgl Exp $ * *------------------------------------------------------------------------- */ @@ -2713,10 +2713,10 @@ insert_ordered_oid(List *list, Oid datum) * Presently, all the catalog and index entries that are referred to * by catcaches are stored in the initialization file. * - * As of v6.5, vacuum.c deletes the initialization file at completion - * of a VACUUM, so that it will be rebuilt at the next backend startup. - * This ensures that vacuum-collected stats for the system catalogs - * and indexes will be seen by backends started later. + * The same mechanism that detects when catcache and relcache entries + * need to be invalidated (due to catalog updates) also arranges to + * unlink the initialization file when its contents may be out of date. + * The file will then be rebuilt during the next backend startup. */ /* -- 2.40.0