inheritance of connection paramters when using \c - Mailing list pgsql-hackers

From nagaura.ryohei@fujitsu.com
Subject inheritance of connection paramters when using \c
Date
Msg-id OSAPR01MB39404FBE8678C185C25D273896E20@OSAPR01MB3940.jpnprd01.prod.outlook.com
Whole thread Raw
List pgsql-hackers
Hello!

\c is followed by [-reuse-previous=on/off] positional syntax | conninfo
Using \c -reuse-previous=on positional syntax or \c positional syntax without -reuse-previous option, some parameters
whichwere omitted or notated as "-" will be reused in the new connection. 
The target is only "dbname", "user", "host", "port" in the current implementation.
# details in [1]
When we discussed in [2], this topic came out.
Although I'm not heavy psql user, I want it to inherit connection parameters and Fabien-san does too.

My new specification:
\c inherits all the unspecified connection parameters in PQconninfoOptions in cases below.
a) \c -reuse-previous=on positional syntax
b) \c positional syntax
This is just an expansion of the target of inheritance of parameters from the current specification.

I have an item to talk about.
It is whether the message which indicates connection information to users has to have more information such as
You are now connected to database "TomANDJelly" as user "nyannyan" with some parameters [reused | defaults].
# after "nyannyan"

Do you have any thoughts?

[1] https://www.postgresql.org/docs/12/app-psql.html
[2] https://www.postgresql.org/message-id/flat/EDA4195584F5064680D8130B1CA91C45367328@G01JPEXMBYT04
Best regards,
---------------------
Ryohei Nagaura




pgsql-hackers by date:

Previous
From: "nagaura.ryohei@fujitsu.com"
Date:
Subject: [patch]socket_timeout in interfaces/libpq
Next
From: Michael Paquier
Date:
Subject: Re: [patch]socket_timeout in interfaces/libpq