Re: Use a separate pg_depend.deptype for extension membership?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Use a separate pg_depend.deptype for extension membership?
Date: 2011-02-04 19:48:06
Message-ID: 17679.1296848886@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> If we go with a new deptype, I was thinking of using 'm' (macro
>> DEPENDENCY_MEMBER) but am not set on that. Have we been using any
>> particular term to refer to the objects that belong to an extension?

> Do you really think the new dependency type has to be re-usable easily
> in the future? DEPENDENCY_EXTENSION ('e') would look fine by me.

Hmm ... Haas suggested that too, but to me it seems confusing: which way
does such a dependency point? But if others don't find it so, I'm
willing to go with the majority.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-02-04 19:48:44 Re: Extensions support for pg_dump, patch v27
Previous Message Robert Haas 2011-02-04 19:46:29 Re: OCLASS_FOREIGN_TABLE support is incomplete