Thread: BUG #5601: cannot create language plperl;
The following bug has been logged online: Bug reference: 5601 Logged by: Rene Novotny Email address: novotny_r@egp.cz PostgreSQL version: 9.0 beta 4 Operating system: Win 7 64 bit Description: cannot create language plperl; Details: ERROR: Could not load library c:/Program Files/PostgreSQL/9.0/lib/plperl.dll unknown error 126 For a memory reasons we need to use 64 bit Windows postgresql , you finally made one. But when we installed Activestate 64 bit perl 5.12 perl ( for 64 bit postgres i suppose 64 bit perl ) it doesn't work. We have thousands of Postgres plperl functions and without working plperl we need to throw away years of work. For us this is a serious bug in PostgreSQL functionality ( plperl and plperlu is the best language that postgres has over all commercial databases ). Please let me know , with what perl you compiled the plperl.dll on windows ( i suppose that ActiveState ). Before the final release of Postgres 9.0 we have to have it solved otherwise it is a disaster for planning engaging Postgres in the infrastructure of our company. Thhanks a lot Rene Novotny UJV REZ software development
On Thu, Aug 5, 2010 at 00:13, Rene Novotny <novotny_r@egp.cz> wrote: > > The following bug has been logged online: > PostgreSQL version: 9.0 beta 4 > Operating system: =C2=A0 Win 7 64 bit > Description: =C2=A0 =C2=A0 =C2=A0 =C2=A0cannot create language plperl; > Details: > > ERROR: Could not load library > c:/Program Files/PostgreSQL/9.0/lib/plperl.dll > unknown error 126 Near as I can tell that means it cant find a .dll or it is incompatible. > For a memory reasons we need to use 64 bit Windows > postgresql , you finally made one. > But when we installed Activestate 64 bit perl 5.12 perl > ( for 64 bit postgres i suppose 64 bit perl ) > it doesn't work. Please let me know , with what > perl you compiled the plperl.dll on windows ( i suppose that ActiveState = ). If you are using the enterprisedb one click installer it looks like you need to grab something that has perl510.dll (maybe activestate 5.10?) Just a guess, I dont have a windows machine here (or really know anything about the windows build) I just downloaded the windows .zip file and skimmed the contents of plperl.dll. Of course you are always welcome to build your own postgresql if you need 5.12.
Thank's a lot with Activestate 64 bit perl 5.10 it works. It would be very desirable for plperl supporter to to add some plperl relea= se notes with Postgresql=20 production release for users to know , with what PERL distribution it works. Rene Novotny >>> Alex Hunsaker 5.8.2010 17:33 >>> On Thu, Aug 5, 2010 at 00:13, Rene Novotny wrote: > > The following bug has been logged online: > PostgreSQL version: 9.0 beta 4 > Operating system: Win 7 64 bit > Description: cannot create language plperl; > Details: > > ERROR: Could not load library > c:/Program Files/PostgreSQL/9.0/lib/plperl.dll > unknown error 126 Near as I can tell that means it cant find a .dll or it is incompatible. > For a memory reasons we need to use 64 bit Windows > postgresql , you finally made one. > But when we installed Activestate 64 bit perl 5.12 perl > ( for 64 bit postgres i suppose 64 bit perl ) > it doesn't work. Please let me know , with what > perl you compiled the plperl.dll on windows ( i suppose that ActiveState = ). If you are using the enterprisedb one click installer it looks like you need to grab something that has perl510.dll (maybe activestate 5.10?) Just a guess, I dont have a windows machine here (or really know anything about the windows build) I just downloaded the windows .zip file and skimmed the contents of plperl.dll. Of course you are always welcome to build your own postgresql if you need 5.12.
On Mon, Aug 9, 2010 at 01:30, Rene Novotny <novotny_r@egp.cz> wrote: > Thank's a lot > > with =C2=A0Activestate 64 bit perl 5.10 it works. > > It would be very desirable for plperl supporter to to add some plperl rel= ease notes with Postgresql > production release for users to know , with what PERL distribution it wor= ks. Yeah, with any luck the enterprisedb people are reading this thread and will fix that. (I imagine its a similar problem with the other pl's like plpython)