| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Gurjeet Singh <gurjeet(at)singh(dot)im> |
| Cc: | Postgres Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql --no-connect option |
| Date: | 2023-08-25 04:20:58 |
| Message-ID: | 20230825042058.jg7nv5mm3smlspkb@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Thu, Aug 24, 2023 at 12:55:30PM -0700, Gurjeet Singh wrote:
> Currently, psql exits if a database connection is not established when
> psql is launched.
>
> Sometimes it may be useful to launch psql without connecting to the
> database. For example, a user may choose to start psql and then pipe
> commands via stdin, one of which may eventually perform the \connect
> command. Or the user may be interested in performing operations that
> psql can perform, like setting variables etc., before optionally
> initiating a connection.
>
> The attached patch introduces the --no-connect option, which allows
> psql to continue operation in absence of connection options.
FTR this has been discussed in the past, see at least [1].
I was interested in this feature, suggesting the exact same "--no-connect"
name, so still +1 for this patch (note that I haven't read it).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2023-08-25 04:26:47 | Re: psql --no-connect option |
| Previous Message | Amit Kapila | 2023-08-25 03:55:47 | Re: subscription/015_stream sometimes breaks |