Re: [GENERAL] freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?

2008-06-30 Thread Tom Lane
hubert depesz lubaczewski <[EMAIL PROTECTED]> writes: > 58241 postgres CALL poll(0x7fffd4e0,0x1,0x7d0) > 58241 postgres RET poll -1 errno 4 Interrupted system call > 58241 postgres CALL poll(0x7fffd4e0,0x1,0x7d0) > 58241 postgres RET poll -1 errno 4 Interrupted system call > 5824

Re: [GENERAL] freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?

2008-06-30 Thread hubert depesz lubaczewski
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

Re: [GENERAL] freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?

2008-06-29 Thread Bill Moran
On Sat, 28 Jun 2008 11:35:24 +0200 hubert depesz lubaczewski <[EMAIL PROTECTED]> wrote: > On Sat, Jun 28, 2008 at 02:22:26AM -0300, Rodrigo Gonzalez wrote: > > So, read man page, and at least ktrace -C and read the output at > > ktrace.out file. > > ok, i've read it and didn't understand. it says

Re: [GENERAL] freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?

2008-06-28 Thread hubert depesz lubaczewski
On Sat, Jun 28, 2008 at 02:22:26AM -0300, Rodrigo Gonzalez wrote: > So, read man page, and at least ktrace -C and read the output at > ktrace.out file. ok, i've read it and didn't understand. it says how to disable tracing but it doesn't say anything about enabling tracing. yesterday ktrace -p p

Re: [GENERAL] freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?

2008-06-28 Thread hubert depesz lubaczewski
On Fri, Jun 27, 2008 at 06:04:19PM -0400, Tom Lane wrote: > Anything unusual about this DB (lots of tables, for instance)? sorry, missed that question - nothing unusual. couple of dbs (10-15), around 20 tables per databases, only 1 database really used - all others tend to be used only for testing

Re: [GENERAL] freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?

2008-06-27 Thread Rodrigo Gonzalez
hubert depesz lubaczewski wrote: > On Fri, Jun 27, 2008 at 06:37:45PM -0400, Bill Moran wrote: >> Just in case you're not a FreeBSD expert, it's ktrace on FreeBSD. strace >> is the Linux equivalent. > > i'm not an freebsd expert. > > i ran ktrace -p - it exited immediately. > then i ran ktrace

Re: [GENERAL] freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?

2008-06-27 Thread hubert depesz lubaczewski
On Fri, Jun 27, 2008 at 06:37:45PM -0400, Bill Moran wrote: > Just in case you're not a FreeBSD expert, it's ktrace on FreeBSD. strace > is the Linux equivalent. i'm not an freebsd expert. i ran ktrace -p - it exited immediately. then i ran ktrace -p -f stats.ktrace.log -t\+ and it also exited

Re: [GENERAL] freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?

2008-06-27 Thread Bill Moran
On Fri, 27 Jun 2008 18:04:19 -0400 Tom Lane <[EMAIL PROTECTED]> wrote: > hubert depesz lubaczewski <[EMAIL PROTECTED]> writes: > > friend asked me to setup replication on their machines, and i noticed > > that one of cpus (2 quad xeons) is used to 100%: > > pgsql 58241 99.0 0.2 22456 7432 ??

Re: [GENERAL] freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?

2008-06-27 Thread Tom Lane
hubert depesz lubaczewski <[EMAIL PROTECTED]> writes: > friend asked me to setup replication on their machines, and i noticed > that one of cpus (2 quad xeons) is used to 100%: > pgsql 58241 99.0 0.2 22456 7432 ?? Rs Thu10AM 1530:35.93 postgres: > stats collector process(postgres) Hmm,

[GENERAL] freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?

2008-06-27 Thread hubert depesz lubaczewski
hi first of all - i know next to nothing about bsd. friend asked me to setup replication on their machines, and i noticed that one of cpus (2 quad xeons) is used to 100%: pgsql 58241 99.0 0.2 22456 7432 ?? Rs Thu10AM 1530:35.93 postgres: stats collector process(postgres) what might be