On Mon, May 14, 2007 at 06:26:42PM +0100, Gregory Stark wrote: > > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > > 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? > > Well currently it's not really terribly interesting to use interactively since > you could always just start a second shell and run a second instance of psql. > I really only have regression tests in mind for it. That's why I don't find it > a problem at all to only extend \g and not semicolon handling. > > That said, I think a next step for this for interactive use would be to handle > C-z to "background" the currently running query. So perhaps it does make sense > to keep use cases like that when deciding on command names now.
Yeah, I think having the ability to open up another connection within psql will turn out to be very useful from an interactive standpoint; \c& (or whatever command we use to duplicate the current connection) is going to be a lot easier to enter than actually starting up a new psql in many production environments. -- Jim Nasby [EMAIL PROTECTED] EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
