Re: Making sure \timing is on - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Making sure \timing is on
Date
Msg-id dcc563d10805112025v676b884bi7bf228685f53e7f3@mail.gmail.com
Whole thread Raw
In response to Re: Making sure \timing is on  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Making sure \timing is on  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Sun, May 11, 2008 at 9:04 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Francisco Reyes <lists@stringsutils.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.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Making sure \timing is on
Next
From: Tom Lane
Date:
Subject: Re: Making sure \timing is on