On Sat, 1 Dec 2007, Tom Lane wrote:
I wrote:
I got around to trying it with a dusty 5.6.1 I have laying about on my
HPPA machine, and the news is not good: CREATE LANGUAGE plperl dumps
core deep inside libperl. With or without this patch.
As best I can tell at the moment, I have not tested 5.6.1 with anything
later than our 7.2 branch, so I don't know exactly where the breakage
slipped in. It may be of long standing.
Actually, libperl seems to dump core in the same place in every PG
version, back to and including 7.2, so what seems more likely is that
this copy of perl is just plain broken. Since we didn't have any form
of regression test for plperl back then, it's entirely possible that
I never tested any further than compiling plperl with that setup.
So we still need someone to try it with a good copy of 5.6 ...
I tested cvs head which includes the patch on Solaris 9/SPARC with perl
5.6.1 and it seems to work fine.
Test output attached.
Steve
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
CREATE OR REPLACE FUNCTION test(TEXT) RETURNS bool language plperl as $$
return (shift =~
/[a-z\u0105\u0107\u0119\u0142\u0144ó\u015b\u017a\u017c\u0104\u0106\u0118\u0141\u0143\u015aÓ\u0179\u017b0-9_-]+/i)
|| 0;
$$;
CREATE FUNCTION
select test('depesz');
test
------
t
(1 row)
select test('depesz\u0105\u0107\u0119\u0142');
test
------
t
(1 row)
select test('depesz\u0105\u0107\u0119\u0142$');
test
------
t
(1 row)
select test('dePEsz\u0105\u0106\u0119\u0142$');
test
------
t
(1 row)
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
