Skip site navigation (1) Skip section navigation (2)

Re: Concurrent psql patch

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Concurrent psql patch
Date: 2007-05-14 17:26:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
"Jim C. Nasby" <decibel(at)decibel(dot)org> 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.

  Gregory Stark

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2007-05-14 17:29:12
Subject: Re: Use of ActiveSnapshot
Previous:From: Andrew - SupernewsDate: 2007-05-14 17:26:05
Subject: Re: What is happening on buildfarm member baiji?

pgsql-patches by date

Next:From: David FetterDate: 2007-05-14 17:35:56
Subject: Re: [PATCHES] OS/X startup scripts
Previous:From: Alvaro HerreraDate: 2007-05-14 16:55:56
Subject: Re: [GENERAL] dropping role w/dependent objects

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group