| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Francisco Reyes <lists(at)stringsutils(dot)com>, PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Making sure \timing is on |
| Date: | 2008-05-12 21:17:06 |
| Message-ID: | 20080512211706.GA22159@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-patches |
On Sun, May 11, 2008 at 11:48:29PM -0400, Tom Lane wrote:
> "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> writes:
> > Is it reasonable behavior to have \timing along toggle and \timing on
> > / \timing off be a forced switch? Just thinking of other scripts
> > where this isn't a problem and having to update them.
>
> The command without an argument should certainly keep the old toggle
> behavior, for backwards compatibility.
Attached patch does some of the right thing, but doesn't yet handle
error cases. How liberal should we be about capitalization, spelling,
etc.?
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
| Attachment | Content-Type | Size |
|---|---|---|
| psql_set_timing.patch | text/plain | 539 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vic Simkus | 2008-05-12 21:18:30 | Re: Recovering database after disk crash |
| Previous Message | Chris Saldanha | 2008-05-12 21:15:01 | Re: changing the endianness of a database |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-05-12 21:30:48 | Re: Making sure \timing is on |
| Previous Message | Andrew Dunstan | 2008-05-12 20:57:01 | odd output in restore mode |