Re: Query runs 38 seconds for small database!

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jan de Visser <jdevisser(at)digitalfairway(dot)com>, pgsql-performance(at)postgresql(dot)org, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
Subject: Re: Query runs 38 seconds for small database!
Date: 2006-05-08 20:02:59
Message-ID: 20060508200258.GJ3351@surnet.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Tom Lane wrote:
> Jan de Visser <jdevisser(at)digitalfairway(dot)com> writes:
> > On Monday 08 May 2006 14:10, Andrus wrote:
> >> I created empty table konto and loaded more that 219 records to it during
> >> database creation.
> >> So it seems that if table grows from zero to more than 219 times larger
> >> then it was still not processed.
>
> > That's because you need at least 500 rows for analyze and 100 for a vacuum,
> > (autovacuum_vacuum_threshold = 1000, autovacuum_analyze_threshold = 500).
>
> This crystallizes something that's been bothering me for awhile,
> actually: why do the "threshold" variables exist at all?

Matthew would know about that -- he invented them. I take no
responsability :-)

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2006-05-08 20:08:40 Re: performance question (something to do w/ parameterized
Previous Message Jeffrey Tenny 2006-05-08 19:51:26 Re: performance question (something to do w/ parameterized