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

From Tom Lane
Subject Re: language cleanups in code and docs
Date
Msg-id 1445281.1592406019@sss.pgh.pa.us
Whole thread Raw
In response to Re: language cleanups in code and docs  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: language cleanups in code and docs  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> On 6/17/20 6:32 AM, Magnus Hagander wrote:
>> In looking at this I realize we also have exactly one thing referred
>> to as "blacklist" in our codebase, which is the "enum blacklist" (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 the hash table, and we definitely change things like that in normal
>> releases with no specific thought on backwards compat).

> I'm not sure I like doing s/Black/Block/ here. It reads oddly. There are
> too many other uses of Block in the sources. Forbidden might be a better
> substitution, or Banned maybe. BanList is even less characters than
> BlackList.

I think worrying about blacklist/whitelist is carrying things a bit far
in the first place.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [Patch] ALTER SYSTEM READ ONLY
Next
From: Robert Haas
Date:
Subject: Re: tablespace_map code cleanup