Re: Re: Monitoring activities of PostgreSQL ("Everlasting" function execution)

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Allan Kamau <kamauallan(at)gmail(dot)com>
Cc: Postgres General Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Re: Monitoring activities of PostgreSQL ("Everlasting" function execution)
Date: 2010-06-16 10:15:23
Message-ID: 4C18A43B.4030208@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 16/06/10 16:56, Allan Kamau wrote:

> The function I have mentioned above seems to "hang" indefinitely (now
> 12hours and counting) while it took only 2secs for the many times it
> was previously invoked from the client application (with slightly
> different parameter value at each such time).

Is there anything in pg_catalog.pg_locks that relates to that query?

If you attach a debugger to the stalled backend and get a backtrace,
what's the output? See:

http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD

If you strace the problem backend, does it appear to be doing anything?

--
Craig Ringer

Tech-related writing: http://soapyfrogs.blogspot.com/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dave Page 2010-06-16 10:19:41 Re: Problem serving one-click installer to Syria
Previous Message maarten 2010-06-16 09:22:15 Re: integer to little endian conversion