Re: moving from contrib to bin

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: moving from contrib to bin
Date: 2014-12-12 16:14:56
Message-ID: CA+TgmoYp6iBh61OL5ZkoWGpn6BCxJyBRb=ObT-h9HyjWboEfnw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 12, 2014 at 11:00 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
>> I'm pretty much -1 on relocating anything that's under src/bin already.

I agree. I can't see packagers putting it anywhere except for
$SOMETHING/bin in the final install, so what do we get out of dividing
it up in some weird way in our tree?

> So let's put the whole bunch under src/bin/ and be done with it.

I'm not really convinced this is a very good idea. What do we get out
of moving everything, or even anything, from contrib? It will make
back-patching harder, but more importantly, it will possibly create
the false impression that everything we distribute is on equal
footing. Right now, we've got stuff like vacuumlo in contrib which is
useful but, let's face it, also a cheap hack. If we decide that
executables can no longer live in contrib, then every time somebody
submits something in the future, we've got to decide whether it
deserves parity with psql and pg_dump or whether we shouldn't include
it at all. contrib is a nice middle-ground.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-12-12 16:15:46 Re: [REVIEW] Re: Compression of full-page-writes
Previous Message Andres Freund 2014-12-12 16:12:10 Re: [REVIEW] Re: Compression of full-page-writes