Re: Concurrent psql patch - Mailing list pgsql-patches

From Jim C. Nasby
Subject Re: Concurrent psql patch
Date
Msg-id 20070514165507.GR69517@nasby.net
Whole thread Raw
In response to Re: Concurrent psql patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Concurrent psql patch  (Gregory Stark <stark@enterprisedb.com>)
Re: Concurrent psql patch  (daveg <daveg@sonic.net>)
List pgsql-patches
On Mon, May 14, 2007 at 11:03:52AM -0400, Tom Lane wrote:
> 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 ...

Since this command will be getting used very frequently by anyone using
concurrent connections interactively, it'd be nice if it was lower-case.
It looks like that limits us to j, k, m, n, v, and y.  In unix this idea
is about jobs, what about using \j?
--
Jim Nasby                                      decibel@decibel.org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Have vacuum emit a warning when it runs out of maintenance_work_mem
Next
From: Alvaro Herrera
Date:
Subject: Re: [GENERAL] dropping role w/dependent objects