Re: Extensions versus pg_upgrade - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Extensions versus pg_upgrade
Date
Msg-id 28100.1297202085@sss.pgh.pa.us
Whole thread Raw
In response to Re: Extensions versus pg_upgrade  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: Extensions versus pg_upgrade
List pgsql-hackers
Dimitri Fontaine <dimitri@2ndQuadrant.fr> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> 2. Invent a command "ALTER EXTENSION extname ADD object-description"
>> that simply adds a pg_depend entry marking an existing object as
>> belonging to the extension.  I think this was going to be part of the
>> plan anyway for ALTER EXTENSION UPGRADE, specifically we need that for
>> the bootstrap case of collecting some loose pre-existing objects into
>> an extension.

> In the upgrade patch, that's spelled ALTER OBJECT foo SET EXTENSION bar;
> and does exactly what you're proposing.

OK, that seems like an equally reasonable syntax; although doing it the
way I was thinking might have less of a code and documentation footprint
(I was vaguely imagining that it could share most of the COMMENT
infrastructure --- but haven't looked yet).  In any case it seems like
this is a good piece to do next, since the required functionality is
clear and it's essential for more than one reason.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: updated patch for foreach stmt
Next
From: Dimitri Fontaine
Date:
Subject: Re: Extensions support for pg_dump, patch v27