# su postgres > cd /usr/lib/postgresql/test/regress > make runtest MULTIBYTE=UNICODE;export MULTIBYTE; \ /bin/sh ./regress.sh linux 2>&1 | tee regress.out ./regress.sh: ../../config.guess: No such file or directory =============== Notes... ================= postmaster must already be running for the regression tests to succeed. The time zone is now set to PST8PDT explicitly by this regression test client frontend. Please report any apparent problems to [EMAIL PROTECTED] See regress/README for more information.
=============== destroying old regression database... ================= =============== creating new regression database... ================= =============== installing PL/pgSQL... ================= Cannot find the file /usr/lib/postgresql/lib/plpgsql.so This shared object contains the call handler for PL/pgSQL. By default, only PL/pgSQL is built and installed. Other languages must be explicitly enabled at configure. so, from /usr/lib/postgresql/test/regress it's looking for ../../config.guess (i.e. /usr/lib/postgresql/config.guess) which is absent (or tardy, at least)... plus, it's unable to locate plpgsql.so, which is apparently playing hookie as well. i tried looking for the package that might have plpgsql, as in > dpkg -S plpgsql postgresql-test: /usr/lib/postgresql/test/regress/sql/install_plpgsql.sql postgresql-test: /usr/lib/postgresql/test/regress/output/install_plpgsql.source postgresql-test: /usr/lib/postgresql/test/regress/sql/plpgsql.sql postgresql-doc: /usr/share/doc/postgresql-doc/src/pl/plpgsql/test postgresql-test: /usr/lib/postgresql/test/regress/expected/install_plpgsql.out postgresql-test: /usr/lib/postgresql/test/regress/expected/plpgsql.out postgresql-doc: /usr/share/doc/postgresql-doc/src/pl/plpgsql postgresql-test: /usr/lib/postgresql/test/regress/input/install_plpgsql.source postgresql-doc: /usr/share/doc/postgresql-doc/src/pl/plpgsql/test/README and you'll notice that none of them contain "plpgsql.>so<"... at first glance (via psql, trying various create/drop, insert/select) postgresql seems healthy, but this test would confirm it.
