| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | "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 03:48:29 |
| Message-ID: | 4691.1210564109@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-patches |
"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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Reece Hart | 2008-05-12 05:27:51 | Re: Scripting function definitions as SQL? |
| Previous Message | Scott Marlowe | 2008-05-12 03:25:54 | Re: Making sure \timing is on |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KaiGai Kohei | 2008-05-12 07:18:54 | Re: [0/4] Proposal of SE-PostgreSQL patches |
| Previous Message | Scott Marlowe | 2008-05-12 03:25:54 | Re: Making sure \timing is on |