Re: InitDB: Bad system call

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: InitDB: Bad system call
Дата
Msg-id 15300.1281626599@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: InitDB: Bad system call  (Torsten Zühlsdorff <foo@meisterderspiele.de>)
Ответы Re: InitDB: Bad system call  (Glen Barber <glen.j.barber@gmail.com>)
Re: InitDB: Bad system call  (Torsten Zühlsdorff <foo@meisterderspiele.de>)
Список pgsql-general
=?ISO-8859-15?Q?Torsten_Z=FChlsdorff?= <foo@meisterderspiele.de> writes:
>> How annoying :-(.  I think what you need to do is use truss or strace
>> or local equivalent with the follow-forks flag, so that you can see what
>> the stand-alone backend process does, not just initdb itself.

> Ok, next round. I just have truss as an option, because strace didn't
> work at my AMD64. Hope its helpfull:

> $ truss -f -o /tmp/pgtuss-f.txt /usr/local/pgsql/bin/initdb -D
> /usr/local/pgsql/data

> Result:
> http://www.dddbl.de/pg-truss-f.txt

[ scratches head ... ]  That looks like it got interrupted before
getting to anything interesting.  Did the console printout show any "Bad
system call" reports?

            regards, tom lane

В списке pgsql-general по дате отправления:

Предыдущее
От: Stephen Cook
Дата:
Сообщение: Re: What does # mean in plpgsql?
Следующее
От: Gary Fu
Дата:
Сообщение: Why DBI (DBD::Pg) takes so much memory ?