Skip site navigation (1) Skip section navigation (2)

Re: plperl/plperlu interaction

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plperl/plperlu interaction
Date: 2006-10-26 20:09:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Andrew Dunstan wrote:
> Tom Lane wrote:
>> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>>        Now suppose we have more than one interpreter instance running
>>> at the
>>>        same time.  This is feasible, but only if you used the
>>> Configure option
>>>        "-Dusemultiplicity" or the options "-Dusethreads
>>> -Duseithreads" when
>>>        building perl.
>>> Now my local perl (FC5/ia64) has usemultiplicity defined. I am not
>>> sure how common this is.
>> Ouch.  It's certainly not the default configuration :-(
> Well, so far many Linux platforms look OK, but FBSD does not.

OpenBSD (which has perl in base) also has those 3 NOT defined ...

> This could be ugly ;-(

yeah ...


In response to

pgsql-hackers by date

Next:From: Josh BerkusDate: 2006-10-26 20:20:32
Subject: Re: plperl/plperlu interaction
Previous:From: Tom LaneDate: 2006-10-26 20:00:49
Subject: Re: Eliminating phase 3 requirement for varlen increases via ALTER COLUMN

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group