| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Torsten Zühlsdorff <foo(at)meisterderspiele(dot)de> |
| 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 15:23:19 |
| Message-ID: | 15300.1281626599@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?ISO-8859-15?Q?Torsten_Z=FChlsdorff?= <foo(at)meisterderspiele(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gary Fu | 2010-08-12 16:15:10 | Why DBI (DBD::Pg) takes so much memory ? |
| Previous Message | Stephen Cook | 2010-08-12 15:19:30 | Re: What does # mean in plpgsql? |