| From: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
|---|---|
| To: | Lucas <lucas75(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: scheduler in core |
| Date: | 2010-02-21 17:04:25 |
| Message-ID: | 4B816799.9040505@cheapcomplexdevices.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Lucas wrote:
> I believe that "in core" may be "installed by default" in case of
Those seem like totally orthogonal concepts to me.
A feature may be "in core" but not "installed by default" (like many PLs).
A feature might not be "in core" but "installed" by many installers (say postgis).
It seems like half the people here are arguing for the former concept.
It seems the other half are arguing against the latter concept.
Is the real need here for a convenient way to enable and/or
recommend packagers to install some non-core modules by default?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-21 17:29:10 | Re: PGXS: REGRESS_OPTS=--load-language=plpgsql |
| Previous Message | Lucas | 2010-02-21 15:17:50 | Re: scheduler in core |