From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: "debug_invalidate_system_caches_always" is too long
Date: Wed, 07 Jul 2021 11:16:57 -0400
Message-ID: <1836635.1625671017@sss.pgh.pa.us> (raw)
In-Reply-To: <a813b3cc-36e6-8f58-273d-ed74be3086b3@enterprisedb.com>
References: <1374320.1625430433@sss.pgh.pa.us>
<a813b3cc-36e6-8f58-273d-ed74be3086b3@enterprisedb.com>
Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> The clobbering doesn't actually happen unless you turn on
> CLOBBER_FREED_MEMORY, so it would be good to keep that separate.
Fair point. What do you think of the alternative proposals
"debug_flush_caches", "debug_discard_caches", etc?
regards, tom lane
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: tgl@sss.pgh.pa.us, peter.eisentraut@enterprisedb.com, pgsql-hackers@lists.postgresql.org
Subject: Re: "debug_invalidate_system_caches_always" is too long
In-Reply-To: <1836635.1625671017@sss.pgh.pa.us>
* 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