Re: Extensions versus pg_upgrade

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Extensions versus pg_upgrade
Date: 2011-02-08 18:18:51
Message-ID: 57204121-2705-49E0-A9A4-6FC2D5A5558D@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Feb 8, 2011, at 10:03 AM, Robert Haas wrote:

> No, this is not doable, or at least not in a way that provides any
> benefit over just dropping and reinstalling. The problem is that it
> is going to fall down all over the place if other objects are
> depending on objects provided by the extension. Like:
>
> CREATE VIEW v AS SELECT extensionfunc(1);

Ah, right, of course. I don't suppose CREATE OR REPLACE would work, either, in some cases at least?

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-02-08 18:24:28 Re: Extensions versus pg_upgrade
Previous Message Tom Lane 2011-02-08 18:06:25 Re: Extensions versus pg_upgrade