From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: More extension issues: ownership and search_path |
Date: | 2011-02-07 19:50:21 |
Message-ID: | 3E9C790A-5231-46CC-B1A0-C6A17B14CE4F@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Feb 7, 2011, at 10:23 AM, Tom Lane wrote:
> On reflection, the set of extensions that an extension depends on is
> obviously a property of the extension, which means it ought to be
> specified in the extension's control file, not in the CREATE EXTENSION
> command. So now I'm thinking something like
>
> requires = 'foo, bar, baz'
>
> in the file.
And that takes us one step closer to PGXN's META.json file. Here's the spec:
It includes a "prereqs" section, which looks like this:
"prereqs": {
"runtime": {
"requires": {
"citext": 0,
"plpgsql": 0,
"PostgreSQL": "8.0.0"
},
"recommends": {
"PostgreSQL": "8.4.0"
}
}
},
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2011-02-07 19:56:28 | Re: Sync Rep for 2011CF1 |
Previous Message | Josh Berkus | 2011-02-07 19:50:02 | Re: Sync Rep for 2011CF1 |