From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Use "superuser" instead of "super user" in code comments |
Date: | 2021-09-08 15:04:49 |
Message-ID: | BEE2A08D-47D3-4084-9245-BE330644FB04@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 7 Sep 2021, at 15:48, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
> On Tue, Sep 7, 2021 at 6:40 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>>
>>> On 7 Sep 2021, at 14:44, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>>
>>> It seems like we use "superuser" as a standard term across the entire
>>> code base i.e. error messages, docs, code comments. But there are
>>> still a few code comments that use the term "super user". Can we
>>> replace those with "superuser"? Attaching a tiny patch to do that.
>>
>> Good catch, superuser is the term we should use for this. There is one
>> additional “super user” in src/test/regress/sql/conversion.sql (and its
>> corresponding resultfile) which can be included in this. Unless there are
>> objections I’ll apply this with the testfile fixup.
>
> Thanks for picking this up. Here's v2 including the change in
> conversion.sql and .out.
Done, thanks!
--
Daniel Gustafsson https://vmware.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2021-09-08 15:06:25 | Re: PoC Refactor AM analyse API |
Previous Message | Wu Haotian | 2021-09-08 14:41:28 | Re: Add option --drop-cascade for pg_dump/restore |