Skip site navigation (1) Skip section navigation (2)

Re: Extensions Dependency Checking

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Aidan Van Dyk <aidan(at)highrise(dot)ca>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extensions Dependency Checking
Date: 2011-04-04 22:57:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Aidan Van Dyk <aidan(at)highrise(dot)ca> writes:
> On Mon, Apr 4, 2011 at 6:06 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> Oh, really? How can you possibly get by without it? Dependencies of
>> this type are all over the place.

> I think the general movement is toward *feature* dependancies.  So for
> intstance, an extension can specify what *feature* it requires, and
> difference "versions" of an extension can provide different
> "features".


> But checking,
> I don't see any "provides" mechanism.

Yes, some sort of manual Provides: (in addition to automatically
extracted Provides:) would likely be part of any serious solution.
We're not there yet, and we're not going to get there in time for 9.1.
But in any case, mechanisms that involve version ordering comparisons
seem to be on their way out for deciding whether package A is
compatible with package B.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2011-04-04 23:04:59
Subject: Re: time table for beta1
Previous:From: Tom LaneDate: 2011-04-04 22:43:00
Subject: Re: Extensions Dependency Checking

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group