From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Install extensions using update scripts (was Re: Remove superuser() checks from pgstattuple) |
Date: | 2016-09-06 02:24:09 |
Message-ID: | 25703.1473128649@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On September 4, 2016 6:33:30 PM PDT, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I think nearly all of the
>> infrastructure for this is already there in extension.c.
> Yes, it doesn't sound very hard...
I poked at this a bit, and indeed it's not that hard. Attached is a
proposed patch (code-complete, I think, but no docs as yet).
Aside from touching CREATE EXTENSION itself, this modifies the
pg_available_extension_versions view to show versions that are installable
on the basis of update chains. I think pg_extension_update_paths() needs
no changes, though.
Ordinarily I'd be willing to stick this on the queue for the next
commitfest, but it seems like we ought to try to get it pushed now
so that Stephen can make use of the feature for his superuser changes.
Thoughts?
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
let-create-extension-follow-update-chains-1.patch | text/x-diff | 11.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2016-09-06 02:26:40 | Re: Install extensions using update scripts (was Re: Remove superuser() checks from pgstattuple) |
Previous Message | Amit Langote | 2016-09-06 01:52:22 | Comment Typo |