Re: Use a separate pg_depend.deptype for extension membership? - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Use a separate pg_depend.deptype for extension membership?
Date
Msg-id m2pqr71stx.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: Use a separate pg_depend.deptype for extension membership?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:
> Dimitri Fontaine <dimitri@2ndQuadrant.fr> writes:
>> 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.

Well the behavior we want is the same as the DEPENDENCY_INTERNAL one, in
about all cases (e.g. DROP SCHEMA CASCADE).  So I think it'd be easier
to stick with doing it the same.  And then the need for specializing the
dependency kind name just raises too…

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


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql
Next
From: Robert Haas
Date:
Subject: Re: more buildfarm breakage