Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m0l40-00036p-Ma for pgsql-hackers@arkaria.postgresql.org; Tue, 06 Jul 2021 13:24:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m0l3y-0004jY-Op for pgsql-hackers@arkaria.postgresql.org; Tue, 06 Jul 2021 13:24:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m0l3y-0004jQ-Hf for pgsql-hackers@lists.postgresql.org; Tue, 06 Jul 2021 13:24:34 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m0l3w-0006ok-BL for pgsql-hackers@lists.postgresql.org; Tue, 06 Jul 2021 13:24:34 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 166DOSFw1664807; Tue, 6 Jul 2021 09:24:28 -0400 From: Tom Lane To: Andrew Dunstan cc: Bharath Rupireddy , Noah Misch , PostgreSQL Hackers Subject: Re: "debug_invalidate_system_caches_always" is too long In-reply-to: <5f1332ab-d2ee-e31d-ecf7-62cc7d150b09@dunslane.net> References: <1374320.1625430433@sss.pgh.pa.us> <20210704211234.GD2421985@rfd.leadboat.com> <1492832.1625512421@sss.pgh.pa.us> <5f1332ab-d2ee-e31d-ecf7-62cc7d150b09@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Tue, 06 Jul 2021 05:50:14 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1664805.1625577868.1@sss.pgh.pa.us> Date: Tue, 06 Jul 2021 09:24:28 -0400 Message-ID: <1664806.1625577868@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan writes: > On 7/5/21 11:46 PM, Bharath Rupireddy wrote: >> On Tue, Jul 6, 2021 at 12:43 AM Tom Lane wrote: >>> I like "debug_flush_caches" --- it's short and accurate. >> Do we always flush the cache entries into the disk? Sometimes we just >> invalidate the cache entries in the registered invalidation callbacks, >> right? Since we already use the term "clobber" in the user visible >> config option --clobber-cache, isn't it consistent to use >> debug_clobber_caches? > I think 'flush' here means simply 'discard'. Maybe that would be a > better word to use. "Discard" could be misinterpreted too, no doubt. None of these words have one single exact meaning, so I have only limited patience for this sort of argumentation. (As for initdb's "--clobber-cache", I'm assuming we'd rename that to match whatever we come up with here. It is what it is now only because I was unwilling to call it "--use-debug-invalidate-system-caches-always".) regards, tom lane