On Sun, Jun 29, 2008 at 05:13:59PM -0400, Bill Moran wrote:
> Use the kdump utility to convert the ktrace.out file to something usable.
> Something like "kdump > ktrace.txt" will probably get you what you want,
> assuming your ktrace file is ktrace.out.
ok. did it. in about 7 seconds, i got 250mb of ktrace.out.
ktrace.txt is 176 megabytes.
content of this is pretty simple:
58241 postgres CALL poll(0x7fffffffd4e0,0x1,0x7d0)
58241 postgres RET poll -1 errno 4 Interrupted system call
58241 postgres CALL poll(0x7fffffffd4e0,0x1,0x7d0)
58241 postgres RET poll -1 errno 4 Interrupted system call
58241 postgres CALL poll(0x7fffffffd4e0,0x1,0x7d0)
58241 postgres RET poll -1 errno 4 Interrupted system call
58241 postgres CALL poll(0x7fffffffd4e0,0x1,0x7d0)
58241 postgres RET poll -1 errno 4 Interrupted system call
58241 postgres CALL poll(0x7fffffffd4e0,0x1,0x7d0)
58241 postgres RET poll -1 errno 4 Interrupted system call
58241 postgres CALL poll(0x7fffffffd4e0,0x1,0x7d0)
58241 postgres RET poll -1 errno 4 Interrupted system call
58241 postgres CALL poll(0x7fffffffd4e0,0x1,0x7d0)
should i make the ktrace.txt available, or should i do something else to
help you ( i mean, the pg-hackers community) diagnose the issue?
Best regards,
depesz