Re: Suggestion for psql command interpretation

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
Thread:
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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-04-15 20:28:22 Re: Suggestion for psql command interpretation
Previous Message Ralph Smith 2008-04-15 20:11:10 I need to ecrypt one column to an output file