| 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>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Use a separate pg_depend.deptype for extension membership? |
| Date: | 2011-02-04 19:51:38 |
| Message-ID: | m2pqr71stx.fsf@2ndQuadrant.fr |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-02-04 20:11:53 | Re: more buildfarm breakage |
| Previous Message | Pavel Stehule | 2011-02-04 19:49:53 | Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql |