Re: modules

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: modules
Date: 2008-04-04 20:27:43
Message-ID: 7837.1207340863@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> On Thu, 3 Apr 2008, Joshua D. Drake wrote:
>> IMO the core modules should be compiled via configure with something
>> like:
>> ./configure --enable-module=ALL

> If you really want to make the problems with using contrib modules go
> away, so they are a) installed even by lazy ISPs who just do
> compile/make/make install, and b) not viewed as second-class citizens when
> people have to ask them to be installed, this won't do it.

Indeed. If anything, this will make the problem worse by increasing the
"perception gap" between contrib modules and modules that don't come
with the core distribution.

IMHO, the ideal situation would be that the only stuff in contrib is
stuff that needs to be maintained together with the core code --- an
example is pg_controldata, because it looks at data structures that
we change on a frequent basis. We need to be looking for ways to
increase the status of stuff that doesn't come with the core distro,
not create an even stronger gap between the "ins" and the "outs".

regards, tom lane

In response to

Responses

  • Re: modules at 2008-04-04 21:17:48 from Andrew Dunstan

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-04-04 20:36:12 Re: Conversion to 8.3
Previous Message Alvaro Herrera 2008-04-04 20:26:08 Re: creating a temp table in a function

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-04-04 20:50:34 Re: modules
Previous Message Tom Dunstan 2008-04-04 20:26:07 Re: modules