Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Anyway, it is probably not expected by many users that loading a module
in plperlu makes it available to plperl - I was slightly surprised
myself to see it work and I am probably more aware than most of perl and
plperl subtleties.
I
Mark Dilger wrote:
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Anyway, it is probably not expected by many users that loading a
module
in plperlu makes it available to plperl - I was slightly surprised
myself to see it work and I am probably more aware than most of perl
and
Jeremy Drake wrote:
On Thu, 26 Oct 2006, Alvaro Herrera wrote:
Jeff Trout wrote:
On Oct 26, 2006, at 3:23 PM, Martijn van Oosterhout wrote:
On Thu, Oct 26, 2006 at 03:15:00PM -0400, Andrew Dunstan wrote:
Perhaps people who use other platforms could look for these
Recently while doing a little research on how we could do perl module
preloading nicely, I constructed the following:
create function loadmods() returns void language plperlu as $$
use LWP::UserAgent;
$$;
select loadmods();
create function loadurl() returns text language plperl as $$
Andrew Dunstan [EMAIL PROTECTED] writes:
Anyway, it is probably not expected by many users that loading a module
in plperlu makes it available to plperl - I was slightly surprised
myself to see it work and I am probably more aware than most of perl and
plperl subtleties.
I think that is a
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Anyway, it is probably not expected by many users that loading a module
in plperlu makes it available to plperl - I was slightly surprised
myself to see it work and I am probably more aware than most of perl and
plperl subtleties.
Andrew Dunstan wrote:
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Anyway, it is probably not expected by many users that loading a
module in plperlu makes it available to plperl - I was slightly
surprised myself to see it work and I am probably more aware than
most of perl
On Thu, Oct 26, 2006 at 03:15:00PM -0400, Andrew Dunstan wrote:
Perhaps people who use other platforms could look for these flags in the
output of
perl -e 'use Config qw(myconfig config_sh config_vars config_re);
print config_sh();'
My Debian Sarge (i386) has:
useithreads='define'
Andrew Dunstan [EMAIL PROTECTED] 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.
On Oct 26, 2006, at 3:23 PM, Martijn van Oosterhout wrote:
On Thu, Oct 26, 2006 at 03:15:00PM -0400, Andrew Dunstan wrote:
Perhaps people who use other platforms could look for these flags
in the
output of
perl -e 'use Config qw(myconfig config_sh config_vars config_re);
print
Jeff Trout wrote:
On Oct 26, 2006, at 3:23 PM, Martijn van Oosterhout wrote:
On Thu, Oct 26, 2006 at 03:15:00PM -0400, Andrew Dunstan wrote:
Perhaps people who use other platforms could look for these flags
in the
output of
perl -e 'use Config qw(myconfig config_sh config_vars
On Thu, Oct 26, 2006 at 03:35:11PM -0400, Jeff Trout wrote:
On Oct 26, 2006, at 3:23 PM, Martijn van Oosterhout wrote:
On Thu, Oct 26, 2006 at 03:15:00PM -0400, Andrew Dunstan wrote:
Perhaps people who use other platforms could look for these flags
in the
output of
perl -e 'use
On Thu, 26 Oct 2006, Alvaro Herrera wrote:
Jeff Trout wrote:
On Oct 26, 2006, at 3:23 PM, Martijn van Oosterhout wrote:
On Thu, Oct 26, 2006 at 03:15:00PM -0400, Andrew Dunstan wrote:
Perhaps people who use other platforms could look for these flags
in the
output of
perl -e
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] 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
Andrew Dunstan wrote:
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] 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
Andrew,
My Debian Sarge (i386) has:
useithreads='define'
usethreads='define'
usemultiplicity='define'
I get the same on Ubuntu and SuSE 9.3, so I think those are pervasive
settings for Linux.
Solaris 10update1:
useithreads='undef'
usethreads='undef'
usemultiplicity='undef'
--
--Josh
On 10/27/06, Jim C. Nasby [EMAIL PROTECTED] wrote:
Undef in Slackware 10.2
Def in Ubuntu 6.06
Undef in Mandriva 2006
Undef in Solaris 10 06
Def in SLES 9.2
Perl 5.8 in SLES 8.1 throws a fit:
Array found where operator expected at
/usr/lib/perl5/5.8.0/warnings.pm line 294, at end of line
Andrej Ricnik-Bay wrote:
On 10/27/06, Jim C. Nasby [EMAIL PROTECTED] wrote:
Undef in Slackware 10.2
Def in Ubuntu 6.06
Undef in Mandriva 2006
Undef in Solaris 10 06
Def in SLES 9.2
Perl 5.8 in SLES 8.1 throws a fit:
Array found where operator expected at
/usr/lib/perl5/5.8.0/warnings.pm line
Andrew Dunstan [EMAIL PROTECTED] writes:
You can also examine the output from perl -V
I think we've already established that we won't be able to ignore the
case of not having support for multiple perl interpreters :-(
So it seems we have these choices:
1. Do nothing (document it as a feature
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
You can also examine the output from perl -V
I think we've already established that we won't be able to ignore the
case of not having support for multiple perl interpreters :-(
So it seems we have these choices:
1. Do nothing
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
3. Support separate interpreters if possible, refuse to run both plperl
and plperlu functions in the same backend if not.
How would we decide which wins in the third case? first in seems
rather arbitrary. If we went that way I'd
21 matches
Mail list logo
