From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: "debug_invalidate_system_caches_always" is too long |
Date: | 2021-07-07 08:37:15 |
Message-ID: | a813b3cc-36e6-8f58-273d-ed74be3086b3@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 04.07.21 22:27, Tom Lane wrote:
> I do agree with the "debug_" prefix given that it's now visible to
> users. However, it doesn't seem that hard to save some space in
> the rest of the name. The word "system" is adding nothing of value,
> and the word "always" seems rather confusing --- if it does
> something "always", why is there more than one level? So a simple
> proposal is to rename it to "debug_invalidate_caches".
I think we can definitely drop the "always". Not so much the "system",
since there are other caches, but it would be ok if we want it shorter.
> However, I think we should also give serious consideration to
> "debug_clobber_cache" or "debug_clobber_cache_always" for continuity
> with past practice (though it still feels like "always" is a good
> word to lose now). "debug_clobber_caches" is another reasonable
> variant.
The clobbering doesn't actually happen unless you turn on
CLOBBER_FREED_MEMORY, so it would be good to keep that separate.
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2021-07-07 08:37:42 | Re: Remove useless int64 range checks on BIGINT sequence MINVALUE/MAXVALUE values |
Previous Message | Peter Eisentraut | 2021-07-07 08:28:38 | Re: PostgreSQL-13.3 parser.y with positional references by named references |