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

help / color / mirror / Atom feed

From: Tobias Brox <tobias@nordicbet.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tobias Brox <tobias@nordicbet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: long running transactions
Date: Tue, 10 Oct 2006 19:13:04 +0200
Message-ID: <20061010171304.GC5360@oppetid.no> (raw)
In-Reply-To: <25953.1160500192@sss.pgh.pa.us>
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>

[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.  Well, whatever, we still have the
nightly vacuum crontab.

view thread (14+ messages)  latest in thread

Message-ID: <20061010171304.GC5360@oppetid.no>
Permalink:  ../20061010171304.GC5360@oppetid.no/
Also on:    postgresql.org/message-id/20061010171304.GC5360@oppetid.no

copy link · copy postgr.es

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: tobias@nordicbet.com, tgl@sss.pgh.pa.us
  Subject: Re: long running transactions
  In-Reply-To: <20061010171304.GC5360@oppetid.no>

* 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