Re: Moving test_fsync to /contrib?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Moving test_fsync to /contrib?
Date: 2011-01-17 17:54:28
Message-ID: 14227.1295286868@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Robert Haas wrote:
>> I confess to some confusion about what things "belong" where.

> I was suggesting /contrib because it seems to be of limited usefulness.
> I assume people want pg_upgrade to stay in /contrib for the same reason.

pg_upgrade is a different issue, really. I think it's in contrib
because we don't trust it fully and don't want to promise that it will
work in every single future release anyway. But even if we moved it to
core, it will always be a special case for packagers: not only is it
not appropriate to put it in the base package, it's not useful to
package it at all unless you also provide a copy of a back-rev
postmaster. So at least for my money it will always be part of its
own special subpackage postgresql-upgrade. (BTW, I just recently got
round to making that work for Fedora.)

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-01-17 17:56:05 Re: Moving test_fsync to /contrib?
Previous Message Kevin Grittner 2011-01-17 17:48:39 Re: READ ONLY fixes