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: Stephen Harris <lists(at)spuddy(dot)org>, "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql possible TODO
Date: 2006-12-05 22:56:46
Message-ID: 15347.1165359406@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:
> !46 seems awful easy to me.

[ shrug... ] Obviously you've learned a different way of doing things.
I suppose there's no point in telling you that another way is better
when you're happy with the one that's already wired into your fingertips.

The main objection I have to the proposal other than not having a use
for it myself is that adding line numbers to \s output destroys the
usefulness of \s for any other purpose than the one you propose. In
particular, you could no longer take a chunk of it and put it into a SQL
script without doing a lot of tedious (and mistake-prone) editing to get
rid of the numbers. Since that's the only use I've ever had for \s, I'm
not happy about losing it.

> Worse yet... what if it is actually query 27 because I got distracted by
> a support question over jabber from the customer I am actually working
> on and I need to help him profile a query for a couple of minutes?

Isn't that an argument *against* using numbers for this?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-12-05 23:03:38 Re: psql possible TODO
Previous Message Svenne Krap 2006-12-05 22:52:58 Re: psql possible TODO