Re: language cleanups in code and docs - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: language cleanups in code and docs
Date
Msg-id CA+hUKGJnN6zWisrOAznSd6O_+WAhCqRwFq4jQowbLtTh-jUihg@mail.gmail.com
Whole thread Raw
In response to Re: language cleanups in code and docs  (Magnus Hagander <magnus@hagander.net>)
Responses Re: language cleanups in code and docs
List pgsql-hackers
On Wed, Jun 17, 2020 at 10:32 PM Magnus Hagander <magnus@hagander.net> wrote:
> In looking at this I realize we also have exactly one thing referred to as "blacklist" in our codebase, which is the
"enumblacklist" (and then a small internal variable in pgindent). AFAICT, it's not actually exposed to userspace
anywhere,so we could probably make the attached change to blocklist at no "cost" (the only thing changed is the name of
thehash table, and we definitely change things like that in normal releases with no specific thought on backwards
compat).

+1

Hmm, can we find a more descriptive name for this mechanism?  What
about calling it the "uncommitted enum table"?  See attached.

Attachment

pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: [PATCH] Add section headings to index types doc
Next
From: Anastasia Lubennikova
Date:
Subject: Re: [patch] Fix checksum verification in base backups for zero page headers