From: Carlo Stonebanks <stonec.register@sympatico.ca>
To: pgsql-performance@postgresql.org
Subject: Re: commit so slow program looks frozen
Date: Sat, 28 Oct 2006 11:51:23 -0400
Message-ID: <ehvu9v$21sq$1@news.hub.org> (raw)
References: <6E0907A94904D94B99D7F387E08C4F570192F2D0@FALCON.INSIGHT>
<ehqhpe$20jt$1@news.hub.org>
<b42b73150610260806le117c55s126585ca6421cb0f@mail.gmail.com>
<1162030022.11568.168.camel@silverbirch.site>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: stonec.register@sympatico.ca
Subject: Re: commit so slow program looks frozen
In-Reply-To: <ehvu9v$21sq$1@news.hub.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox