CreateLang80 » History » Version 2
Álvaro Herrera, 11/16/2005 05:07 PM
1 | 1 | Álvaro Herrera | = Creating the PL/php language in a PostgreSQL 8.0 database = |
---|---|---|---|
2 | |||
3 | In 8.0 you need to create the PL/php language using these commands: |
||
4 | |||
5 | {{{ |
||
6 | CREATE FUNCTION plphp_call_handler() RETURNS language_handler |
||
7 | LANGUAGE C AS '$libdir/plphp', 'plphp_call_handler'; |
||
8 | |||
9 | CREATE TRUSTED LANGUAGE plphp |
||
10 | 2 | Álvaro Herrera | HANDLER plphp_call_handler; |
11 | 1 | Álvaro Herrera | |
12 | CREATE LANGUAGE plphpu |
||
13 | 2 | Álvaro Herrera | HANDLER plphp_call_handler; |
14 | 1 | Álvaro Herrera | }}} |
15 | (note you '''DON'T''' have to edit the $libdir. Leave it alone. It will be expanded by PostgreSQL automatically.) |
||
16 | |||
17 | This will create entries for the trusted and untrusted versions of PL/php. Note that you need to repeat these steps in every database you want to use PL/php in. You may want to create it in the template1 database so that it's automatically created in new databases. |
||
18 | |||
19 | Now the language is ready to be used. |
||
20 | |||
21 | If you receive an error similar to: |
||
22 | |||
23 | {{{ |
||
24 | ERROR: could not load library "/usr/local/lib/postgresql/plphp.so": |
||
25 | libphp4.so: cannot open shared object file: No such file or directory |
||
26 | }}} |
||
27 | |||
28 | it means the Postmaster can't find the PHP shared library. A solution |
||
29 | you may use is to define the LD_LIBRARY_PATH to postmaster, like so: |
||
30 | |||
31 | {{{ |
||
32 | LD_LIBRARY_PATH=/usr/lib/apache2/modules:$LD_LIBRARY_PATH postmaster |
||
33 | }}} |
||
34 | |||
35 | Of course this isn't ideal. You may want to define the variable somewhere in your start script (/etc/init.d/postgresql or whatever). This is too varied across Linux distributions or other operating systems so I'll leave it as an exercise to the reader. |