Re: Extensions versus pg_upgrade

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Extensions versus pg_upgrade
Date: 2011-02-10 16:58:56
Message-ID: m2oc6jltbj.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> That would be rejected because you're not allowed to drop an individual
> member object of an extension. (And no, I don't want to have a kluge in
> dependency.c that makes that test work differently when
> creating_extension.)

Fair enough, all the more as soon as we have ALTER EXTENSION DROP :)

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-02-10 17:01:42 Re: Why we don't want hints Was: Slow count(*) again...
Previous Message Kevin Grittner 2011-02-10 16:45:20 Re: Why we don't want hints Was: Slow count(*) again...