From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Francisco Reyes <lists(at)stringsutils(dot)com>, PostgreSQL general <pgsql-general(at)postgresql(dot)org>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Making sure \timing is on |
Date: | 2008-05-13 23:11:01 |
Message-ID: | 7719.1210720261@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
David Fetter <david(at)fetter(dot)org> writes:
> On Tue, May 13, 2008 at 11:36:57AM -0400, Tom Lane wrote:
>>> Uh, my point was that the agreement was to do this to *all* of
>>> psql's toggling backslash commands, not only \timing.
>>
>> Done :)
Hmm, I thought we had a lot more than three that were like this.
But on looking closer, I guess all the other ones are \pset boolean
options that already behave properly.
Actually, \a and \H are fairly bogus anyway, because they are "toggling"
a setting that has more than two values. I wonder whether defining the
argument as a boolean is really very sane. Perhaps it would be better to
take the argument if given as just a regular format setting --- ie,
with an argument, either of these would just be a shorthand for
\pset format.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Thatcher | 2008-05-13 23:33:33 | Re: Alias in the HAVING clause |
Previous Message | David Wilson | 2008-05-13 23:01:12 | Re: Alias in the HAVING clause |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-05-14 00:43:19 | Re: stored procedure stats in collector |
Previous Message | Pavel Stehule | 2008-05-13 22:22:24 | Re: options for RAISE statement |