La version del Postgres es la 8.4.7 Donde puedo mirar lo del "multiplicity"... No domino mucho esto
-----Mensaje original----- De: Alvaro Herrera [mailto:alvhe...@alvh.no-ip.org] Enviado el: jueves, 07 de abril de 2011 16:29 Para: Aitor Cincunegui Perez CC: pgsql-es-ayuda Asunto: Re: [pgsql-es-ayuda] Error createlang plperlu Excerpts from Aitor Cincunegui Perez's message of jue abr 07 07:31:44 -0300 2011: > Buenas, > > Estoy trabajando bajo plataforma Windows y querría vincular tablas de SQL > Server. Tengo instalado el PostgreSQL 8.4 y el ActivePerl 5.10. > Mirando documentación por internet, he visto que debo utilizar dbi-link. > Uno de los primeros pasos que mencionan es crear el lenguaje PLPERLU y aqui > viene mi problemilla. > Me da el siguiente error: > > createlang -U postgres plperlu geopista > > createlang: falló la instalación del lenguaje: > ERROR: Can't locate vars.pm in @INC (@INC contains: .) at -e line 1. > BEGIN failed--compilation aborted > CONTEXTO: mientras se interpretaba la inicialización de Perl Hmm, ¿qué versión exacta de Postgres estás usando? Si es 8.4.5 o posterior quizás esto se deba a un bug introducido en este cambio: (Fíjate si tu Perl tiene la opción "multiplicity") commit b805be2587972c153dbc047dc2cc74edef92a36d Author: Tom Lane <t...@sss.pgh.pa.us> Date: Thu Sep 30 17:20:25 2010 -0400 Use a separate interpreter for each calling SQL userid in plperl and pltcl. There are numerous methods by which a Perl or Tcl function can subvert the behavior of another such function executed later; for example, by redefining standard functions or operators called by the target function. If the target function is SECURITY DEFINER, or is called by such a function, this means that any ordinary SQL user with Perl or Tcl language usage rights can do essentially anything with the privileges of the target function's owner. To close this security hole, create a separate Perl or Tcl interpreter for each SQL userid under which plperl or pltcl functions are executed within a session. However, all plperlu or pltclu functions run within a session still share a single interpreter, since they all execute at the trust level of a database superuser anyway. Note: this change results in a functionality loss when libperl has been built without the "multiplicity" option: it's no longer possible to call plperl functions under different userids in one session, since such a libperl can't support multiple interpreters in one process. However, such a libperl already failed to support concurrent use of plperl and plperlu, so it's likely that few people use such versions with Postgres. Security: CVE-2010-3433 -- Álvaro Herrera <alvhe...@alvh.no-ip.org> - Enviado a la lista de correo pgsql-es-ayuda (pgsql-es-ayuda@postgresql.org) Para cambiar tu suscripción: http://www.postgresql.org/mailpref/pgsql-es-ayuda
