From: Noah Misch <noah@leadboat.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: "debug_invalidate_system_caches_always" is too long
Date: Fri, 9 Jul 2021 04:12:11 -0700
Message-ID: <20210709111211.GB2945708@rfd.leadboat.com> (raw)
In-Reply-To: <2042257.1625776495@sss.pgh.pa.us>
References: <1374320.1625430433@sss.pgh.pa.us>
<a813b3cc-36e6-8f58-273d-ed74be3086b3@enterprisedb.com>
<1836635.1625671017@sss.pgh.pa.us>
<CA+TgmoZtjhH=Gqp6E_ybMk0bjZ-D4dht-KYRRzyeLaOHVR5S5Q@mail.gmail.com>
<2042257.1625776495@sss.pgh.pa.us>
On Thu, Jul 08, 2021 at 04:34:55PM -0400, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > On Wed, Jul 7, 2021 at 11:17 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> Fair point. What do you think of the alternative proposals
> >> "debug_flush_caches", "debug_discard_caches", etc?
>
> > I like debug_discard_caches best.
>
> I can live with that. Anyone strongly against it?
I like it.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: noah@leadboat.com, tgl@sss.pgh.pa.us, robertmhaas@gmail.com, peter.eisentraut@enterprisedb.com, pgsql-hackers@lists.postgresql.org
Subject: Re: "debug_invalidate_system_caches_always" is too long
In-Reply-To: <20210709111211.GB2945708@rfd.leadboat.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox