Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Are we losing momentum?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sean Chittenden <sean(at)chittenden(dot)org>
Cc: Curt Sampson <cjs(at)cynic(dot)net>, Brent Verner <brent(at)rcfile(dot)org>,pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Are we losing momentum?
Date: 2003-04-16 16:26:58
Message-ID: 19469.1050510418@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-generalpgsql-hackerspgsql-patches
Sean Chittenden <sean(at)chittenden(dot)org> writes:
> 4) guc.c is now in sync with the list of available variables used for
> tab completion
>> 
>> AFAIK, the GUC variables not listed in tab-complete.c were omitted
>> deliberately.  We could have a discussion about the sensefulness of
>> those decisions, but please do not consider it a bug to be fixed
>> out-of-hand.

> Alright, there weren't many omitted GUC's, but those that were
> omitted did have counterparts that were include already so I figured
> there was some bit rot going on.

There could be some of that too.  I was just saying that it's not a
foregone conclusion to me that every parameter known to guc.c should
be in the tab completion list.

			regards, tom lane


In response to

pgsql-hackers by date

Next:From: Rob ButlerDate: 2003-04-16 16:39:58
Subject: Re: cross-db queries (was Are we losing momentum?)
Previous:From: Jonathan BartlettDate: 2003-04-16 16:24:30
Subject: Re: high availability

pgsql-patches by date

Next:From: Peter EisentrautDate: 2003-04-16 17:47:18
Subject: Re: [PATCHES] the build
Previous:From: Barry LindDate: 2003-04-16 16:25:47
Subject: Re: [PATCHES] the build

pgsql-advocacy by date

Next:From: Josh BerkusDate: 2003-04-16 16:32:23
Subject: Novice needs help in Portuguese-BR
Previous:From: Josh BerkusDate: 2003-04-16 16:20:31
Subject: Now we need French help

pgsql-general by date

Next:From: Bruno Wolff IIIDate: 2003-04-16 16:50:29
Subject: Re: calculating time
Previous:From: Jonathan BartlettDate: 2003-04-16 16:24:30
Subject: Re: high availability

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group