Re: psql tabcomplete - minor bugfix - tabcomplete for SET ROLE TO xxx - Mailing list pgsql-hackers

From Andres Freund
Subject Re: psql tabcomplete - minor bugfix - tabcomplete for SET ROLE TO xxx
Date
Msg-id 20150908163339.GF5084@alap3.anarazel.de
Whole thread Raw
In response to Re: psql tabcomplete - minor bugfix - tabcomplete for SET ROLE TO xxx  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: psql tabcomplete - minor bugfix - tabcomplete for SET ROLE TO xxx  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 2015-09-08 07:06:04 +0200, Pavel Stehule wrote:
> 2015-09-07 21:44 GMT+02:00 Andres Freund <andres@anarazel.de>:
> > The spellings for boolean values were a relatively small subset of what
> > the backend accepts - it's now on,off,true,false,yes,no,1,0. I'm not
> > sure whether that's a good idea. Comments?
> >
> 
> if somebody prefer true, false, and we will support only on, off, then the
> tabcomplete will not be too user friendly :(
> 
> "1, 0" can be out - but other?

After sleeping on it I think we should keep all of them - they'll show
for lots of "boolean like" GUCs (e.g. constraint_exclusion, sync_commit,
huge_pages) so not showing them for booleans just seems
inconsisten. Unless somebody protests pdq I'll push it that way.

Andres



pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Memory Context Info dump
Next
From: Robert Haas
Date:
Subject: Re: gin_fuzzy_search_limit and postgresql.conf.sample