| Lists: | pgsql-general |
|---|
| From: | Colin Wetherbee <cww(at)denterprises(dot)org> |
|---|---|
| To: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Suggestion for psql command interpretation |
| Date: | 2008-04-15 18:02:21 |
| Message-ID: | 4804EDAD.9060700@denterprises.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
I just made a typo in psql, and it resulted in something I wouldn't have
expected.
js=# \timimng
Showing only tuples.
js=# \t
Tuples only is off.
I also wouldn't have expected \timimng to have been interpreted as
\timing, which I tried to type in the first place, but perhaps a typo
like this should throw an error?
Colin
| From: | Colin Wetherbee <cww(at)denterprises(dot)org> |
|---|---|
| To: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Suggestion for psql command interpretation |
| Date: | 2008-04-15 18:06:51 |
| Message-ID: | 4804EEBB.4070204@denterprises.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
Colin Wetherbee wrote:
> I just made a typo in psql, and it resulted in something I wouldn't have
> expected.
Oh, um, this was in the 8.3.1 psql.
Colin
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Colin Wetherbee <cww(at)denterprises(dot)org> |
| Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Suggestion for psql command interpretation |
| Date: | 2008-04-15 18:40:25 |
| Message-ID: | 1411.1208284825@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
Colin Wetherbee <cww(at)denterprises(dot)org> writes:
> I just made a typo in psql, and it resulted in something I wouldn't have
> expected.
> js=# \timimng
> Showing only tuples.
This is related to the discussion about whether to require a space
between a backslash command name and its arguments ...
regards, tom lane
| From: | Colin Wetherbee <cww(at)denterprises(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Suggestion for psql command interpretation |
| Date: | 2008-04-15 20:25:09 |
| Message-ID: | 48050F25.5000404@denterprises.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
Tom Lane wrote:
> Colin Wetherbee <cww(at)denterprises(dot)org> writes:
>> I just made a typo in psql, and it resulted in something I
>> wouldn't have expected.
>
>> js=# \timimng Showing only tuples.
>
> This is related to the discussion about whether to require a space
> between a backslash command name and its arguments ...
I see.
So, this was interpreted by psql in the same way "\t imimng" would
have been? Not that \t does anything with arguments, though...
I just thought I'd report it here in case it wasn't supposed to
happen, but from what you say, it seems like it's a "feature".
Colin
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Colin Wetherbee <cww(at)denterprises(dot)org> |
| Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Suggestion for psql command interpretation |
| Date: | 2008-04-15 20:28:22 |
| Message-ID: | 5229.1208291302@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
Colin Wetherbee <cww(at)denterprises(dot)org> writes:
> I just thought I'd report it here in case it wasn't supposed to
> happen, but from what you say, it seems like it's a "feature".
Well, it's more of a historical hangover. Personally I'd not have
much problem with breaking backward compatibility on this point.
regards, tom lane
| From: | Colin Wetherbee <cww(at)denterprises(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Suggestion for psql command interpretation |
| Date: | 2008-04-15 20:46:25 |
| Message-ID: | 48051421.70206@denterprises.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
Tom Lane wrote:
> Colin Wetherbee <cww(at)denterprises(dot)org> writes:
>> I just thought I'd report it here in case it wasn't supposed to
>> happen, but from what you say, it seems like it's a "feature".
>
> Well, it's more of a historical hangover. Personally I'd not have
> much problem with breaking backward compatibility on this point.
I'm not generally in the habit of making typos, so this doesn't affect
me too much.
However, IMHO and as I mentioned previously, I don't think "\timimng"
should succeed. I'll leave the rest of the discussion up to you and
the other developers, though. :)
Colin
| From: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my> |
|---|---|
| To: | Colin Wetherbee <cww(at)denterprises(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Suggestion for psql command interpretation |
| Date: | 2008-04-16 18:01:11 |
| Message-ID: | 200804161806.m3GI6QEj097931@smtp5.jaring.my |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
At 04:46 AM 4/16/2008, Colin Wetherbee wrote:
>Tom Lane wrote:
>>Colin Wetherbee <cww(at)denterprises(dot)org> writes:
>>>I just thought I'd report it here in case it wasn't supposed to
>>>happen, but from what you say, it seems like it's a "feature".
>>Well, it's more of a historical hangover. Personally I'd not have
>>much problem with breaking backward compatibility on this point.
>
>I'm not generally in the habit of making typos, so this doesn't
>affect me too much.
>
>However, IMHO and as I mentioned previously, I don't think
>"\timimng" should succeed. I'll leave the rest of the discussion up
>to you and the other developers, though. :)
I too agree that \timimng should not work.
Maybe someone can think of an undesirable surprise that springs from
this "feature" ;).
\i
\e
Are possible candidates (probably others could clobber files given a typo).
I think requiring a space between command and arguments would be a
good idea. And not doing stuff if there are syntax errors...
Link.