pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: PostgreSQL <martin@portant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 8.1beta3 performance
Date: Wed, 02 Nov 2005 09:41:14 -0500
Message-ID: <5353.1130942474@sss.pgh.pa.us> (raw)
In-Reply-To: <dka140$1rt4$1@news.hub.org>
References: <dk68ku$2lqa$1@news.hub.org>
	<20051101085037.1b12b077@fc63r41.npci.com>
	<26529.1130865883@sss.pgh.pa.us>
	<dka140$1rt4$1@news.hub.org>

"PostgreSQL" <martin@portant.com> writes:
> I'm seeing some other little oddities in the beta as well.  I'm watching an 
> ALTER TABLE ADD COLUMN right now that has been running almost two hours.  I 
> stopped it the first time at 1 hour; I suppose I'll let it go this time and 
> see if it ever completes.  The table is about 150K rows.  Top, vmstat, and 
> iostat show almost no cpu or disk activity (1 to 3%) - it's as if it just 
> went to sleep.

You sure it's not blocked on a lock?  Check pg_locks ... if that sheds
no light, try attaching to the backend process with gdb and getting a
stack trace.

			regards, tom lane



view thread (8+ messages)

Message-ID: <5353.1130942474@sss.pgh.pa.us>
Permalink:  ../5353.1130942474@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/5353.1130942474@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, martin@portant.com
  Subject: Re: 8.1beta3 performance
  In-Reply-To: <5353.1130942474@sss.pgh.pa.us>

* 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