Re: pg_migrator mention in documentation - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pg_migrator mention in documentation
Date
Msg-id 20090703182505.GB4699@alvh.no-ip.org
Whole thread Raw
In response to Re: pg_migrator mention in documentation  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_migrator mention in documentation
List pgsql-hackers
Bruce Momjian wrote:

> I am happy to remove the USE_PGXS from the Makefile, but it seems all
> the other extensions require that so I want to be consistent.

Consistency here is pointless.  IIRC the dual method is used in contrib
because people did not trust the PGXS stuff enough to rip the original
Make code out; or maybe because people did not want PGXS to become the
default build method, but they allowed it to be used in contrib as a
test bed that PGXS worked.  As I pointed out earlier, this nonsense has
crept out to external modules without better reason than being copied
from contrib.

The only problem I see with PGXS is that it cannot be used in certain
situations where you want to have custom rules, but this is seldom the
case.  It would be better to get requests for PGXS enhancements so that
it'd support those other cases too.

Having PGXS is very useful to allow external modules to be built easily.
Being forced to support the "in tree" method *plus* PGXS is pointless.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: PGXS problem with pdftotext
Next
From: Robert Haas
Date:
Subject: Re: [pgsql-www] commitfest.postgresql.org