Re: [PATCHES] WIP 2 interpreters for plperl - Mailing list pgsql-hackers

From Jim Buttafuoco
Subject Re: [PATCHES] WIP 2 interpreters for plperl
Date
Msg-id 200611202054.kAKKs4vG025145@amanda.contactbda.com
Whole thread Raw
In response to Re: [PATCHES] WIP 2 interpreters for plperl  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] WIP 2 interpreters for plperl
List pgsql-hackers
I might be one of the ones who depends on the same interpreter.  In your new
scheme, the _SHARED hash will only be shared between like interpreters,
correct?  This is going to force me to switch all of my perl code to use the
plperlu interpreter :(





-----Original Message-----
From: pgsql-hackers-owner@postgresql.org
[mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Tom Lane
Sent: Monday, November 20, 2006 2:10 PM
To: Andrew Dunstan
Cc: PostgreSQL-development
Subject: Re: [HACKERS] [PATCHES] WIP 2 interpreters for plperl 

Andrew Dunstan <andrew@dunslane.net> writes:
>> Since this is a behaviour modification, do we want to apply it to the 
>> back branches? Doing so would certainly be possible, although it would 
>> be non-trivial.

> I have committed this to HEAD at any rate, so that we can get some 
> buildfarm testing going.

My vote is to leave it just in HEAD; there may be someone out there
depending on plperl and plperlu being in the same interpreter, and
breaking their code in a minor release doesn't seem very friendly.
        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate      subscribe-nomail command to
majordomo@postgresql.orgso that your      message can get through to the mailing list cleanly
 




pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: XA support (distributed transactions)
Next
From: "Simon Riggs"
Date:
Subject: Re: Custom Data Type Question