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

Re: Policy on pulling in code from other projects?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Policy on pulling in code from other projects?
Date: 2011-07-23 17:35:41
Message-ID: 4E2B066D.7080006@commandprompt.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 07/22/2011 05:00 PM, Josh Berkus wrote:
> Arguments in favor of coding from scratch:
>
> 1) Does not introduce new dependencies into postgresql-client packages.
> (note how much of a problem Readline has been)

Readline has license issues, this doesn't.

>
> 2) keeps psql as lightweight as possible
>

Agreed on that one.


> 3) We don't need to be able to parse any potential URI, just the ones we
> accept.

True.

>
> Arguments against:
>
> a) waste of time coding a parser
>
> b) eventual feature creep as people ask us for more and more syntax support

Yep.

>
> Overall, though, I'd say that argument (1) against is pretty powerful.
> Count the number of complaints and build bug reports about readline&
> libedit on the lists.
>

That is a good argument.



-- 
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
The PostgreSQL Conference - http://www.postgresqlconference.org/
@cmdpromptinc - @postgresconf - 509-416-6579

In response to

pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2011-07-23 17:36:57
Subject: Re: Policy on pulling in code from other projects?
Previous:From: Marc MunroDate: 2011-07-23 16:57:26
Subject: Re: [GENERAL] Dropping extensions

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