Re: moving from contrib to bin - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: moving from contrib to bin
Date
Msg-id 20141209211002.GR1768@alvh.no-ip.org
Whole thread Raw
In response to moving from contrib to bin  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: moving from contrib to bin  (Bruce Momjian <bruce@momjian.us>)
Re: moving from contrib to bin  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut wrote:

> Here are the contrib programs:
> 
> oid2name
> pg_archivecleanup
> pg_standby
> pg_test_fsync
> pg_test_timing
> pg_upgrade
> pg_xlogdump
> pgbench
> vacuumlo
> 
> The proposal would basically be to mv contrib/$x src/bin/$x and also
> move the reference pages in the documentation.

Maybe it makes sense to have a distinction between client programs and
server programs.  Can we have src/sbin/ and move stuff that involves the
server side in there?  I think that'd be pg_xlogdump, pg_archivecleanup,
pg_upgrade, pg_test_timing, pg_test_fsync.  (If we were feeling bold we
could also move pg_resetxlog, pg_controldata and initdb there.)

(For pg_upgrade you also need to do something about pg_upgrade_support,
which is good because that is one very ugly crock.)

I agree that oid2name and vacuumlo need to be in a better state to
deserve their promotion to src/bin, if we keep them at all.

In any case I support the move out of contrib of everything except
vacuumlo and oid2name, for reasons already stated by others in the
thread.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: advance local xmin more aggressively
Next
From: Alex Shulgin
Date:
Subject: Re: Small TRUNCATE glitch