Re: Concurrent psql patch - Mailing list pgsql-patches

From Tom Lane
Subject Re: Concurrent psql patch
Date
Msg-id 11752.1179155032@sss.pgh.pa.us
Whole thread Raw
In response to Re: Concurrent psql patch  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Concurrent psql patch  ("Jim C. Nasby" <decibel@decibel.org>)
List pgsql-patches
Gregory Stark <stark@enterprisedb.com> writes:
> But these kinds of inconsistent behaviours can be traps for users. It means
> "\c1" and "\c 1" do different things even though "\cpostgres" and \c postgres"
> do the same thing. And it means "\c1" might connect to a database named "1"
> today but switch sessions tomorrow.

The real problem here is trying to overload an existing command name
with too many different meanings.  You need to pick some other name
besides \c.

If you were willing to think of it as "switch session" instead of "connect",
then \S is available ...

            regards, tom lane

pgsql-patches by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Concurrent psql patch
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Have vacuum emit a warning when it runs out of maintenance_work_mem