At 04:46 AM 4/16/2008, Colin Wetherbee wrote:
Tom Lane wrote:
Colin Wetherbee <[EMAIL PROTECTED]> 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
Tom Lane wrote:
Colin Wetherbee <[EMAIL PROTECTED]> 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 com
Colin Wetherbee <[EMAIL PROTECTED]> 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 th
Tom Lane wrote:
Colin Wetherbee <[EMAIL PROTECTED]> 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 argu
Colin Wetherbee <[EMAIL PROTECTED]> 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 ...
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
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/p
