From: PriceGoblin Accounts <accounts@pricegoblin.co.uk>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Should autovacuum do a database wide vacuum near transaction limit?
Date: Sat, 22 Jan 2011 09:46:33 -0000
Message-ID: <E1EDB59A3C4E4ACE915899E5A5FC3B36@squarepi.com> (raw)
References: <927BF3A3F54247FF8C63219A00CE98B5@squarepi.com>
<1427.1295651046@sss.pgh.pa.us>
<A83ED098FF4346FFBA6AB8A2AA46A218@squarepi.com>
<2081.1295653238@sss.pgh.pa.us>
<4D3AA304.7070506@kickstone.com>
<AANLkTik++ug_RYscONWu8xfBHR9438YyryvvbMcs0nS0@mail.gmail.com>
>> Was this expected behaviour with temporary tables?
>It's more expected behavior when you have long running transactions.
>I haven't seen it caused by temp tables. Was the parent process in a
>really long transaction or just open a long time without one?
The first thing I checked was for open transactions, but alas there were
none. I suspect the process had been
open a long time without creating any transactions, but don't know which
process it was at this point, the connection
was owned by my colleague so need to check with him or look for dead
applications...
John
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-admin@postgresql.org
Cc: accounts@pricegoblin.co.uk, scott.marlowe@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: Should autovacuum do a database wide vacuum near transaction limit?
In-Reply-To: <E1EDB59A3C4E4ACE915899E5A5FC3B36@squarepi.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