Re: Making sure \timing is on

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:25:54
Message-ID: dcc563d10805112025v676b884bi7bf228685f53e7f3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-patches

On Sun, May 11, 2008 at 9:04 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Francisco Reyes <lists(at)stringsutils(dot)com> writes:
>> Tom Lane writes:
>>> Not that I know of :-(. There's been discussion of fixing all of psql's
>>> "toggle" commands to offer "\foo on" and "\foo off"
>
>> What would be a good starting point for someone interesting in looking into
>> working on that?
>
> This'd be a fine starting project IMHO, if you can read/code C at all.
> The rubber meets the road in exec_command() in src/bin/psql/command.c
> --- look around in that area. In particular note that ParseVariableBool
> in variables.c probably ought to be what you use to interpret the
> meaning of the argument.

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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-05-12 03:48:29 Re: Making sure \timing is on
Previous Message Tom Lane 2008-05-12 03:04:33 Re: Making sure \timing is on

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2008-05-12 03:48:29 Re: Making sure \timing is on
Previous Message Tom Lane 2008-05-12 03:04:33 Re: Making sure \timing is on