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

plperl function has side-effects

From: Joachim Wieland <joe(at)mcknight(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Subject: plperl function has side-effects
Date: 2005-03-03 16:41:36
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

I have a 7.4.3 installation where a small plperl function seems to have
side-effects. In the example below I run an ordinary SELECT first, nothing
special with the table. Thereafter I call the plperl function and then I
rerun the SELECT query. This time it doesn't return the expected result. The
problem seems to show up only after postgres has run for quite a while.
Futhermore this effect is limited to the current session. I'll upgrade the
machine to 7.4.7 during the weekend, however I haven't seen anything in the
release notes that seems to matter, does anybody know this effect or is this
issue even already solved?

(Crypt::PasswdMD5 1.3, perl 5.8.4)

db=> select login from subaccounts where login='web1p1';
(1 row)

db=> select md5password('bla1', 'Ao2ZaGKp');
(1 row)

db=> select login from subaccounts where login='web1p1';
(0 rows)

The definition of md5password:

CREATE FUNCTION md5password(varchar(20), varchar(50)) RETURNS varchar(50)
use Crypt::PasswdMD5;

my $password = $_[0];
my $salt = $_[1];

my $crypted = unix_md5_crypt($password, $salt);

return $crypted;
' LANGUAGE 'plperlu';


pgsql-hackers by date

Next:From: Tom LaneDate: 2005-03-03 16:56:32
Subject: Re: 8.0.X and the ARC patent
Previous:From: pgsqlDate: 2005-03-03 16:41:20
Subject: Re: bitmap AM design

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