pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tobias Brox <tobias@nordicbet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: long running transactions
Date: Tue, 10 Oct 2006 13:18:27 -0400
Message-ID: <26123.1160500707@sss.pgh.pa.us> (raw)
In-Reply-To: <20061010171304.GC5360@oppetid.no>
References: <20061010161027.GA18908@oppetid.no>
	<25404.1160497420@sss.pgh.pa.us>
	<20061010163913.GA8097@oppetid.no>
	<20061010164142.GA5360@oppetid.no>
	<25631.1160498572@sss.pgh.pa.us>
	<20061010170639.GB5360@oppetid.no>
	<25953.1160500192@sss.pgh.pa.us>
	<20061010171304.GC5360@oppetid.no>

Tobias Brox <tobias@nordicbet.com> writes:
> [Tom Lane - Tue at 01:09:52PM -0400]
>> Hmph.  Is the autovac process actually doing anything (strace would be
>> revealing)?  If not, can you attach to the autovac process with gdb and
>> get a stack trace to see where it's blocked?

> Sorry ... I SIGINT'ed it, and now it's gone :-(  I thought reloading the
> config would restart autovacuum.

It'll come back after the autovacuum naptime.  If it gets stuck again,
please investigate.

			regards, tom lane



view thread (14+ messages)  latest in thread

Message-ID: <26123.1160500707@sss.pgh.pa.us>
Permalink:  ../26123.1160500707@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/26123.1160500707@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, tobias@nordicbet.com
  Subject: Re: long running transactions
  In-Reply-To: <26123.1160500707@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