Re: [GENERAL] psql \pset pager - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [GENERAL] psql \pset pager
Date
Msg-id 200805062134.m46LYng10880@momjian.us
Whole thread Raw
In response to Re: [GENERAL] psql \pset pager  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [GENERAL] psql \pset pager  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > So, I think the answer is that we have the current behavior because of
> > backward compatibility.  Perhaps we should be more strict in
> > ParseVariableBool(), perhaps only allowing true/false and on/off.
> 
> If we're going to change it, we should make it match GUC's parse_bool,
> which has had some actual thought put into it.

Good idea.  Do I copy the C code into /psql or somehow share the
function?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: statement timeout vs dump/restore
Next
From: Tom Lane
Date:
Subject: Re: [0/4] Proposal of SE-PostgreSQL patches