Re: Extensions vs. shared procedural language handler functions

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Extensions vs. shared procedural language handler functions
Date: 2011-03-05 14:51:21
Message-ID: m2oc5ppqmu.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:
> I can imagine that someplace down the road we might want to allow
> multiple extensions to own the same SQL object; I know that RPMs can
> share ownership of files, for comparison. But today is not that day.
[…]
> Anyone have a different answer?

What could be done is to have a common extension that installs the
functions, then both plperl and plperlu would require the common bits.
That's only practical when we have automatic dependency resolution at
install and remove times (it should not be hard to do, but well).

So for 9.1, I think you took the simplest path available.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-03-05 14:54:05 Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)
Previous Message Andy Colson 2011-03-05 14:44:24 Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)