Re: Making tab-complete.c easier to maintain - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Making tab-complete.c easier to maintain
Date
Msg-id 20151023000943.GP14196@alap3.anarazel.de
Whole thread Raw
In response to Re: Making tab-complete.c easier to maintain  (David Fetter <david@fetter.org>)
Responses Re: Making tab-complete.c easier to maintain  (Robert Haas <robertmhaas@gmail.com>)
Re: Making tab-complete.c easier to maintain  (David Fetter <david@fetter.org>)
List pgsql-hackers
On 2015-10-22 16:26:10 -0700, David Fetter wrote:
> To be affective negatively by libreadline's viral license, an entity
> would need to fork the psql client in proprietary ways that they did
> not wish not to make available to end users, at the same time linking
> in libreadline.

> Maybe I'm missing something big, but I really don't see people out
> there shipping a libreadline-enabled psql client, details of whose
> source they'd want to keep a deep, dark secret.

Isn't that just about every proprietary fork of postgres? Most have
added backend features and I guess many of those have in turn added
support to psql for those features.  Sure it'd probably in reality be
relatively harmless for them to release these psql modifications, but I
rather doubt their management will generally see it that way.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Avoid full page images in streaming replication?
Next
From: Noah Misch
Date:
Subject: Re: Re: [BUGS] BUG #13611: test_postmaster_connection failed (Windows, listen_addresses = '0.0.0.0' or '::')