On 01.11.22 22:31, David G. Johnston wrote:
This is the only sentence I claim is factually incorrect, with a
suggested re-wording.
committed
This is the only sentence I claim is factually incorrect, with a suggested
re-wording.
diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml
index 9494f28063..f375a0fc11 100644
--- a/doc/src/sgml/ref/psql-ref.sgml
+++ b/doc/src/sgml/ref/psql-ref.sgml
@@ -660,7 +660,8 @@ EOF
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 resol
On Sat, Jul 9, 2022, 08:16 Bruce Momjian wrote:
> On Sat, Jul 9, 2022 at 08:06:21AM -0700, David G. Johnston wrote:
> > Maybe invoke the wording from the libpq docs and say:
> >
> > The default database name is the same as the user connection parameter.
> >
> >
> https://www.postgresql.org/docs/
On Sat, Jul 9, 2022 at 08:06:21AM -0700, David G. Johnston wrote:
> Maybe invoke the wording from the libpq docs and say:
>
> The default database name is the same as the user connection parameter.
>
> https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-PARAMKEYWORDS
>
> That page
On Friday, July 8, 2022, Bruce Momjian wrote:
> On Fri, Jul 8, 2022 at 10:17:11PM -0400, Tom Lane wrote:
> > Bruce Momjian 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
On Fri, Jul 8, 2022 at 10:17:11PM -0400, Tom Lane wrote:
> Bruce Momjian 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
> >> data
Bruce Momjian 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
On Tue, Jul 5, 2022 at 08:20:25PM -0400, Tom Lane wrote:
> "David G. Johnston" writes:
> > In passing, the authentication error examples use the phrase
> > "database user name" in a couple of locations. The word
> > database in both cases is both unusual and unnecessary for
> > u
On 06.07.22 14:30, Matthias van de Meent wrote:
If we're going to change this anyway, could we replace 'user name'
with 'username' in the connection documentation? It irks me to see so
much 'user name' while our connection parameter is 'username', and we
use the username of the OS user, not the O
On Wed, 6 Jul 2022 at 02:43, David G. Johnston
wrote:
>
> On Tue, Jul 5, 2022 at 5:20 PM Tom Lane wrote:
>>
>> "David G. Johnston" writes:
>> > In passing, the authentication error examples use the phrase
>> > "database user name" in a couple of locations. The word
>> > database in
On Tue, Jul 5, 2022 at 5:20 PM Tom Lane wrote:
> "David G. Johnston" writes:
> > In passing, the authentication error examples use the phrase
> > "database user name" in a couple of locations. The word
> > database in both cases is both unusual and unnecessary for
> > understand
"David G. Johnston" writes:
> In passing, the authentication error examples use the phrase
> "database user name" in a couple of locations. The word
> database in both cases is both unusual and unnecessary for
> understanding. The reference to user name means the one in/for the
>
13 matches
Mail list logo
