| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Standardize GetTokenInformation() error reporting. |
| Date: | 2016-04-07 03:50:15 |
| Message-ID: | E1ao0xT-0001LY-Oo@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Standardize GetTokenInformation() error reporting.
Commit c22650cd6450854e1a75064b698d7dcbb4a8821a sparked a discussion
about diverse interpretations of "token user" in error messages. Expel
old and new specimens of that phrase by making all GetTokenInformation()
callers report errors the way GetTokenUser() has been reporting them.
These error conditions almost can't happen, so users are unlikely to
observe this change.
Reviewed by Tom Lane and Stephen Frost.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/f2b1b3079ce9d2965f6e450585f24d18cdf5647b
Modified Files
--------------
src/backend/libpq/auth.c | 8 ++++----
src/port/win32security.c | 4 ++--
src/test/regress/pg_regress.c | 4 ++--
3 files changed, 8 insertions(+), 8 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-04-07 04:47:28 | Re: pgsql: Generic Messages for Logical Decoding |
| Previous Message | Stephen Frost | 2016-04-07 03:43:31 | Re: [COMMITTERS] pgsql: Use GRANT system to manage access to sensitive functions |