Skip site navigation (1) Skip section navigation (2)

Re: commit so slow program looks frozen

From: "Carlo Stonebanks" <stonec(dot)register(at)sympatico(dot)ca>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: commit so slow program looks frozen
Date: 2006-10-28 15:51:23
Message-ID: ehvu9v$21sq$1@news.hub.org (view raw or flat)
Thread:
Lists: pgsql-performance
> I do think we need some better instrumentation for this kind of thing.

Well, one thing's for sure - I have little other information to offer. The 
problem is that the lockups occur after hours of operation and thousands of 
rows being digested (which is the nature of the program). If "better 
instrumentation" implies tools to inpsect the sate of the db server's 
process and to know what it's waiting for from the OS, I agree.

Then again, I can't even tell you whether the postgres process is at fault 
or the TCL interface - which would be odd, because it's one fo the most 
mature interfaces postgres has. So, here's a thought: is there any way for 
me to inspect the state of a postgres process to see if it's responsive - 
even if it's serving another connection?

Carlo 



In response to

pgsql-performance by date

Next:From: Merlin MoncureDate: 2006-10-28 17:39:58
Subject: Re: commit so slow program looks frozen
Previous:From: Carlo StonebanksDate: 2006-10-28 15:45:37
Subject: Re: commit so slow program looks frozen

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group