| From: | Torsten Zühlsdorff <foo(at)meisterderspiele(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: InitDB: Bad system call |
| Date: | 2010-08-12 14:04:35 |
| Message-ID: | 4C63FF73.2000606@meisterderspiele.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Tom,
>> Please notice, that after changing the IPC-Settings of the system, no
>> core-file is dumped anymore. Quiet interessting.
>
> 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
Greetings,
Torsten
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitriy Igrishin | 2010-08-12 14:35:13 | TOO MANY CONNECTIONS (53300) |
| Previous Message | Tom Lane | 2010-08-12 13:36:11 | Re: InitDB: Bad system call |