| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
| Cc: | "pgsql-patches" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: \timing on/off |
| Date: | 2008-06-10 15:02:45 |
| Message-ID: | 17614.1213110165@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
"Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> writes:
>> I gather that the conclusion of the thread "Making sure \timing is on",
>> starting at:
>> http://archives.postgresql.org/pgsql-general/2008-05/msg00324.php
>>
>> was that we should leave \H and \a alone for now, because it's not clear
>> what "\H off" would do.
Yeah, I think that was the consensus.
>> Here's a patch, based on David's patch, that turns timing into a \pset
>> variable, and makes \timing an alias for \pset timing. This makes
>> \timing behave the same as \x.
This seems a bit random to me. AFAIR all of the \pset properties are
associated with formatting of table output. \timing doesn't belong.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-06-10 15:09:57 | Re: SQL: table function support |
| Previous Message | Heikki Linnakangas | 2008-06-10 14:49:45 | Refactoring xlogutils.c |