Robert,
As a first attempt, set log_min_duration_statement to 0 in your
configuration file and restart the service, do not forget to tail your
log file in order to understand what is going on. There are other
parameter that will help you identify potential problems, all of them
related with log_*. RTFM! :)
Another tip, Process Explorer, a tool for Windows that shows all
the stuff running in windows such as the Linux 'ps' program but with a
fancy UI. It's a freeware tool, so try it. It should present you the
PID of the offending process; this PID plus some SQL magic and the
pg_stat_* tables will let you know what's going on.
2 cents
gb.-
On Sat, Jan 24, 2009 at 3:01 PM, Robert Schnabel <schnabelr@missouri.edu> wrote:
> Hi all, I recently noticed that I have a postgres.exe process running at
> 100% CPU but is not doing any I/O. This is fresh off of starting the
> service. This is a local db so I am the only one using it and it will do
> this even if I do not have any queries running. I have let it run for about
> 2 days (not running any queries) but it never stops so I figured I'd ask for
> some advice. I upgraded to 8.2.11 about a month ago and haven't had any
> issues so this seems to be a recent development within the last week. I
> guess my question is how should I go about tracking down the cause of this
> running wild? I'm running Win XP64 SP2, Postgre 8.2.11.
>
> Thanks in advance for any pointers.
> Bob
>
>
> --
> Sent via pgsql-novice mailing list (pgsql-novice@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-novice
>
