|From:||Bruce Momjian <bruce(at)momjian(dot)us>|
|To:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Fri, Jul 8, 2022 at 10:17:11PM -0400, Tom Lane wrote:
> 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.
Well, one confusion is that there is a database name and a database user
name. We don't have different operating system names that users can
connect to, usually.
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
Indecision is a decision. Inaction is an action. Mark Batterson
|Next Message||Bruce Momjian||2022-07-09 02:55:55||Re: doc: Clarify Routines and Extension Membership|
|Previous Message||Jingtang Zhang||2022-07-09 02:18:45||Re: Two successive tabs in test case are causing syntax error in psql|