Re: Pgsql taking a *lot* of CPU time (unkillable).

From: Berteun Damman <berteun(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Pgsql taking a *lot* of CPU time (unkillable).
Date: 2005-01-15 19:40:34
Message-ID: 8d25d48a0501151140272f2330@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, 15 Jan 2005 13:15:36 -0500, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Would you attach to the process with a debugger and get a stack trace?
>
> $ gdb /usr/pkg/bin/postgres PID-of-process
> gdb> bt
> gdb> q
>
> Probably should repeat this a few times to get a clear sense of where
> it's looping.

I think it has a locking problem:
#0 0x483bbb2e in pthread__lock_ras_end () from /usr/lib/libpthread.so.0
Error accessing memory address 0x483bbb26: Operation not permitted.

And the other time:
#0 0x483bbb31 in pthread__lock_ras_end () from /usr/lib/libpthread.so.0
And again an accessing error.

Does this indicate an error in NetBSD's pthreading library?

Berteun

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message ntinos 2005-01-15 19:50:35 Re: PQisBusy() always returns TRUE
Previous Message PFC 2005-01-15 19:20:04 Re: OID Usage