Re: Naming of gss_accept_deleg
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Abhijit Menon-Sen <ams@toroid.org>, Stephen Frost <sfrost@snowman.net>, pgsql-hackers@postgresql.org
Date: 2023-05-21T01:33:44Z
Lists: pgsql-hackers
On Fri, May 19, 2023 at 07:58:34AM -0700, Nathan Bossart wrote: > On Fri, May 19, 2023 at 09:42:00AM -0400, Tom Lane wrote: > > Abhijit Menon-Sen <ams@toroid.org> writes: > >> I would also prefer a GUC named gss_accept_delegation, but the current > >> name matches the libpq gssdeleg connection parameter and the PGSSDELEG > >> environment variable. Maybe there's something to be said for keeping > >> those three things alike? > > > > +1 for spelling it out in all user-visible names. I do not think > > that that GSS-API C symbol is a good precedent to follow. > > +1 With less then 48 hours to beta 1 packaging, I have made this change and adjusted internal variable to match. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.
Commits
-
Spell the values of libpq's gssdelegation parameter as "0" and "1".
- 1f9f6aa49198 16.0 landed
-
Expand some more uses of "deleg" to "delegation" or "delegated".
- a2eb99a01e01 16.0 landed
-
Fix remaining references to gss_accept_deleg.
- f4001a553770 16.0 landed
-
rename "gss_accept_deleg" to "gss_accept_delegation".
- 9c0a0e2ed92a 16.0 landed