pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brian Hurt <bhurt@janestcapital.com>
To: Carlo Stonebanks <stonec.register@sympatico.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: commit so slow program looks frozen
Date: Wed, 25 Oct 2006 16:18:51 -0400
Message-ID: <453FC6AB.5090105@janestcapital.com> (raw)
In-Reply-To: <ehog68$19d3$1@news.hub.org>
References: <eho0sj$2eht$1@news.hub.org>
	<20061025181910.GW26407@alvh.no-ip.org>
	<ehog68$19d3$1@news.hub.org>

Carlo Stonebanks wrote:

>>You may try to figure out what's the process doing (the backend
>>obviously, not the frontend (Tcl) process) by attaching to it with
>>strace.
>>    
>>
>
>It's so sad when us poor Windows guys get helpful hints from people assume 
>that we're smart enough to run *NIX... ;-)
>
>  
>
>>Maybe it's swamped by a context switch storm (but in that case, probably 
>>the other processes would be affected as well).
>>    
>>
>
>What is a context switch storm? (and what a great name for a heavy metal 
>rock band!)
>
>Interestingly enough, last night (after the original post) I watched three 
>of the processes slow down, one after the other - and then stall for so long 
>that I had assumed they had frozen. They were all stalled on a message that 
>I had put in the script that indicated they had never returned from a 
>commit. I have looked into this, and I believe the commits are actually 
>going through.
>  
>
I have a question for you: did you have a long running query keeping 
open a transaction?  I've just noticed the same problem here, but things 
cleaned up immediately when I aborted the long-running transaction.

Note that in my case the long-running transaction wasn't idle in 
transaction, it was just doing a whole lot of work.

Brian

view thread (22+ messages)  latest in thread

Message-ID: <453FC6AB.5090105@janestcapital.com>
Permalink:  ../453FC6AB.5090105@janestcapital.com/
Also on:    postgresql.org/message-id/453FC6AB.5090105@janestcapital.com

 · 

reply

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: bhurt@janestcapital.com, stonec.register@sympatico.ca
  Subject: Re: commit so slow program looks frozen
  In-Reply-To: <453FC6AB.5090105@janestcapital.com>

* 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