Re: psql possible TODO

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql possible TODO
Date: 2006-12-05 22:45:13
Message-ID: 200612052245.kB5MjDf26529@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera wrote:
> Tom Lane wrote:
> > "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> > > control-R isn't real useful for 17 queries that are exactly the same
> > > except for 3 different join clauses. It also isn't useful when you don't
> > > know exactly what query you are looking for.
> >
> > ... but, somehow, you know exactly what command number it has?
>
> Well, presumably \s would give you the numbers. "history" does on bash anyway.
>
> I use it on bash all the time: I do "history | grep something" and then
> !<number of command I want>.
>
> I don't think we can do the "| grep" part, but it's useful anyway.

OK, now at least I understand how it would be used, and could be
explained easily in the documentation --- do \s, then \! 99, or maybe \#
99. I don't like making \! do shells and pull SQL commands from history.

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2006-12-05 22:46:54 Re: psql possible TODO
Previous Message Joshua D. Drake 2006-12-05 22:43:44 Re: psql possible TODO