Re: Concurrent psql patch - Mailing list pgsql-patches

From Jim C. Nasby
Subject Re: Concurrent psql patch
Date
Msg-id 20070513222212.GB69517@nasby.net
Whole thread Raw
In response to Re: Concurrent psql patch  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Concurrent psql patch
Re: Concurrent psql patch
List pgsql-patches
On Sun, May 13, 2007 at 02:39:45PM +0100, Gregory Stark wrote:
> "Jim Nasby" <decibel@decibel.org> writes:
>
> > I don't see how we could make the names shorter without moving away from a
> > backslash command (which I'm guessing would be painful).
> >
> > Assuming we're stuck with a backslash command \cs[witch] and \cn
> > [owait] seem to be about as good as we could get.
>
> I don't have \cs or \cn set up as abbreviations.
>
> I was originally thinking \c1, \c2, ... for \cswitch and \c& for \cnowait. I'm
> not sure if going for cryptic short commands is better or worse here.

Would \c# limit us to 9 concurrent connections? Might want

\cs[witch] [session]

which would switch to the specified session. If none specified, it would
switch back to whatever session was previously active.

\c& sounds fine (as do \c1...\c9). \g& would probably be helpful as well
(send query buffer to server in nowait mode).
--
Jim Nasby                                      decibel@decibel.org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

pgsql-patches by date:

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