Re: psql possible TODO

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql possible TODO
Date: 2006-12-05 21:01:34
Message-ID: 11050.1165352494@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Hello,
> A reasonable simple feature we were thinking about sponsoring was an
> addition to psql. Currently if you perform a \s within psql it gives
> you the query buffer. My suggestion is that \s give us a execution
> number, similar to bash. Thus at a psql prompt we could do:

> foo=> !76

> And it would execute whatever query was number 76. Secondly:

> foo=> !!76

> Would execute an explain on whatever query was 76. Lastly:

> foo=> !(at)76

> Would execute an explain analyze within a transaction and a rollback (so
> we could do updates/deletes).

Surely you must use backslash commands for this. Or had you forgotten
that ! and @ are legal operator characters in Postgres?

Also, you can't take away the existing functionality of \s. Invent some
other command instead.

But lastly, do we need this at all? It seems like a relatively awkward,
highly error-prone way to do what you can do today with control-P and
re-execute.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2006-12-05 21:13:04 Re: psql possible TODO
Previous Message Simon Riggs 2006-12-05 21:01:21 Re: [HACKERS] Configuring BLCKSZ and XLOGSEGSZ (in 8.3)