Re: unexplained autovacuum to prevent wraparound

From: Gordon Shannon <gordo169(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: unexplained autovacuum to prevent wraparound
Date: 2010-03-14 20:11:50
Message-ID: b2dd93301003141311w4cc0090oa0fd02c78b7802d2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

That looks like the fix for this, thanks! I will try to upgrade soon.

-- Gordon

On Sun, Mar 14, 2010 at 7:43 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com>wrote:

> Gordon Shannon escribió:
> > Ah, now I see what you meant. Forgive me, I thought you were referring
> to
> > the pg_autovacuum table in 8.3 where you have to specifiy something for
> each
> > column, and -1 says use the default. It appears in 8.4.0 I have to
> > explicitly set ALL (?) other storage parameters to -1 to get the default,
> > otherwise I am getting zero for each value?? I don't believe the
> > documentation mentions this rather important detail:
> >
> http://www.postgresql.org/docs/8.4/static/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS
> .
> > Did I miss it somewhere?
>
> Err, no, that would be a bug. Please update to 8.4.2, I think we fixed
> it there.
>
> revision 1.28.2.1
> date: 2009-08-27 13:19:31 -0400; author: alvherre; state: Exp; lines:
> +10 -10;
> Fix handling of autovacuum reloptions.
>
> In the original coding, setting a single reloption would cause default
> values to be used for all the other reloptions. This is a problem
> particularly for autovacuum reloptions.
>
> Itagaki Takahiro
>
>
> --
> Alvaro Herrera
> http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2010-03-14 20:22:38 Re: OIDs depending data -- how to dump/restore?
Previous Message fkater@googlemail.com 2010-03-14 20:09:37 Re: OIDs depending data -- how to dump/restore?