From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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-07-09 02:17:11 |
Message-ID: | 3591128.1657333031@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Tue, Jul 5, 2022 at 08:20:25PM -0400, Tom Lane wrote:
>> I agree this phrasing needs some work, but "resolved" doesn't seem
>> helpful, since it's not defined here or nearby. Maybe "The default
>> database name is the specified (or defaulted) user name." ?
> I am not seeing much improvement in the proposed patch either. I wonder
> if we should be calling this the "session" or "connection" user name.
> When the docs say "if you do not specify a database name, it defaults to
> the database user name", there is so much "database in there that the
> meaing is unclear, and in this context, the user name is a property of
> the connection or session, not of the database.
Umm ... you could make the exact same statement with respect to the
user's operating-system login session, so I doubt that "session" or
"connection" adds any clarity.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jingtang Zhang | 2022-07-09 02:18:45 | Re: Two successive tabs in test case are causing syntax error in psql |
Previous Message | Tom Lane | 2022-07-09 02:07:46 | Re: Eliminating SPI from RI triggers - take 2 |