From: John Lister <john.lister@kickstone.com>
To: 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: Fri, 21 Jan 2011 23:42:31 -0000
Message-ID: <F4C8E4FB28FD48AD860E030A0A27BC62@squarepi.com> (raw)
References: <927BF3A3F54247FF8C63219A00CE98B5@squarepi.com>
<1427.1295651046@sss.pgh.pa.us>
<A83ED098FF4346FFBA6AB8A2AA46A218@squarepi.com>
<2081.1295653238@sss.pgh.pa.us>
> "John Lister" <john.lister-ps@kickstone.com> writes:
>> On another bizarre note, A database wide vacuum has just finished, but
>> I'm
>> still getting the warnings:
>
>> GMT WARNING: database "backend" must be vacuumed within 10205310
>> transactions
>
> Did you do that vacuum as a superuser?
yes
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: john.lister@kickstone.com, tgl@sss.pgh.pa.us
Subject: Re: Should autovacuum do a database wide vacuum near transaction limit?
In-Reply-To: <F4C8E4FB28FD48AD860E030A0A27BC62@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