Re: Allow \pset to parse "on or off" for boolean values - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: Allow \pset to parse "on or off" for boolean values
Date
Msg-id 200702261823.l1QINT322352@momjian.us
Whole thread Raw
In response to Allow \pset to parse "on or off" for boolean values  ("Chad Wagner" <chad.wagner@gmail.com>)
List pgsql-patches
Your patch has been added to the PostgreSQL unapplied patches list at:

    http://momjian.postgresql.org/cgi-bin/pgpatches

It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.

---------------------------------------------------------------------------


Chad Wagner wrote:
> This is a TODO item:
>
>         o Allow psql \pset boolean variables to set to fixed values, rather
>           than toggle
>
>
> Basically allows for:
> test=# \pset expanded on
> Expanded display is on.
> test=# \pset footer off
> Default footer is off.
> test=# \pset footer
> Default footer is on.
> test=# \pset footer
> Default footer is off.
> test=# \pset footer
> Default footer is on.
>
>
> Basically the change is to check if value in do_pset is != NULL to call
> ParseVariableBool to get a true/false and set the value directly, of the
> second parameter is not provided then the "old logic" of toggling is
> supported.
>
> The pset variables that are adjusted are:
> expanded
> numericlocale
> tuples_only
> pager (supports on/off/always now)
> footer

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>                http://www.postgresql.org/docs/faq

--
  Bruce Momjian  <bruce@momjian.us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-patches by date:

Previous
From: Gregory Stark
Date:
Subject: Numeric patch to add special-case representations for < 8 bytes
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Deadlock with pg_dump?