Обсуждение: Current CVS - something broken in contrib

Поиск
Список
Период
Сортировка

Current CVS - something broken in contrib

От
Teodor Sigaev
Дата:
In any contrib module 'make installcheck' runs infinite time...

For example, contrib/ltree
% gmake installcheck
gmake -C ../../src/test/regress pg_regress
gmake[1]: Вход в каталог `/spool/home/teodor/pgsql/src/test/regress'
gmake[1]: `pg_regress' не требует обновления.
gmake[1]: Выход из каталог `/spool/home/teodor/pgsql/src/test/regress'
../../src/test/regress/pg_regress ltree
(using postmaster on Unix socket, default port)
============== dropping database "regression"         ==============
DROP DATABASE
============== creating database "regression"         ==============
CREATE DATABASE
ALTER DATABASE
============== dropping regression test user accounts ==============
============== installing PL/pgSQL                    ==============
============== running regression test queries        ==============
test ltree                ...

In this time in top:
CPU states:  100% user,  0.0% nice,  0.0% system,  0.0% interrupt,  0.0% idle
Mem: 116M Active, 33M Inact, 24M Wired, 11M Cache, 29M Buf, 1528K Free
Swap: 510M Total, 32M Used, 477M Free, 6% Inuse
kill  PID USERNAME PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU COMMAND
18180 teodor    64   0  1852K  1248K RUN      1:15 95.07% 93.65% psql

postmaster doesn't take a CPU time...


-- 
Teodor Sigaev
teodor@stack.net




Re: Current CVS - something broken in contrib

От
Tom Lane
Дата:
Teodor Sigaev <teodor@stack.net> writes:
> In any contrib module 'make installcheck' runs infinite time...

Looks like my fault :-( ... will have it fixed in a few minutes
(I seem to have broken psql for COPY FROM STDIN :-()
        regards, tom lane


Re: Current CVS - something broken in contrib

От
Tom Lane
Дата:
Teodor Sigaev <teodor@stack.net> writes:
> In any contrib module 'make installcheck' runs infinite time...

Actually, I had managed to break \copy, not COPY --- it seems the
main regression tests exercise COPY but not \copy.  It might be
a good idea to change copy2.sql to exercise both ...

Anyway, fix committed.
        regards, tom lane