| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: doc: Fix description of how the default user name is chosen |
| Date: | 2022-10-31 13:41:45 |
| Message-ID: | d0e91a7c-9b21-8335-c14d-f80f077f102b@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09.07.22 17:52, David G. Johnston wrote:
> No. It is always the user parameter. It just so happens that parameter
> also has a default. And so while there is a transitive aspect the
> resolution of the user parameter happens first, using the OS user if
> needed, then the dbname parameter is resolved using the user parameter
> if needed to supply the default.
Will there be an updated patch here? The original patch contained three
hunks; I'm not sure which one of those was intending to fix a real bug
and which ones were cosmetic. Is anything in the current documentation
actually wrong?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-10-31 13:43:05 | Re: warn if GUC set to an invalid shared library |
| Previous Message | Justin Pryzby | 2022-10-31 13:31:20 | Re: warn if GUC set to an invalid shared library |