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 05:35:20 |
Message-ID: | b2dd93301003132135r2c555b3bx26f1d50e27689b65@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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?
Thanks!
Gordon
On Fri, Mar 12, 2010 at 4:45 PM, Gordon Shannon <gordo169(at)gmail(dot)com> wrote:
> This is 8.4, there is no pg_autovacuum table. I set it like this:
>
> alter table foo set (autovacuum_analyze_scale_factor=0.01);
>
>
>
>
> On Fri, Mar 12, 2010 at 4:31 PM, Alvaro Herrera <
> alvherre(at)commandprompt(dot)com> wrote:
>
>> Gordon Shannon escribió:
>>
>> > One possibly interesting thing is that this seems to have started just
>> after
>> > I set foo's autovacuum_analyze_scale_factor to 0.01, since I wanted more
>> > frequent analyze runs. I wonder if that could be related.
>>
>> You probably set the other values to 0, which includes the freeze age.
>> You need to set it (and all other values) to -1 instead.
>>
>> --
>> Alvaro Herrera
>> http://www.CommandPrompt.com/
>> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>>
>
>
>
--
If I had more time, I could have written you a shorter letter. (Blaise
Pascal)
From | Date | Subject | |
---|---|---|---|
Next Message | A B | 2010-03-14 08:54:09 | Options for fsync? |
Previous Message | Belka Lambda | 2010-03-14 00:24:11 | Is there any easy way to determine a default value specified for table column? |