Re: Extensions vs. shared procedural language handler functions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jan Urbański <wulczer(at)wulczer(dot)org>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Extensions vs. shared procedural language handler functions
Date: 2011-03-05 01:49:32
Message-ID: 29976.1299289772@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

=?UTF-8?B?SmFuIFVyYmHFhHNraQ==?= <wulczer(at)wulczer(dot)org> writes:
> ITYM plperl only, because plpython does not have a trusted variant. But
> there might be another obstacle here: plpython comes in two variants:
> plpython2u and plpython3u, and which one is built depends on the compile
> time configuration. Not sure how that plays with extensions...

Sorry, you're right, that issue is actually plpythonu and plpython2u
sharing the same handler. It's basically the same problem though.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-03-05 03:44:20 Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)
Previous Message Jan Urbański 2011-03-05 01:19:07 Re: Extensions vs. shared procedural language handler functions