Re: Performance Optimization for Dummies 2 - the SQL

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, Carlo Stonebanks <stonec(dot)register(at)sympatico(dot)ca>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Performance Optimization for Dummies 2 - the SQL
Date: 2006-10-08 20:36:27
Message-ID: 20061008203627.GL72517@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Oct 06, 2006 at 02:53:35PM -0400, Merlin Moncure wrote:
> On 10/6/06, Scott Marlowe <smarlowe(at)g2switchworks(dot)com> wrote:
> >On Fri, 2006-10-06 at 11:44, Carlo Stonebanks wrote:
> >> This didn't work right away, but DID work after running a VACUUM FULL. In
> >> other words, i was still stuck with a sequential scan until after the
> >> vacuum.
> >>
> >> I turned autovacuum off in order to help with the import, but was
> >perfoming
> >> an ANALYZE with every 500 rows imported.
>
> how did you determine that it is done every 500 rows? this is the
> default autovacuum paramater. if you followed my earlier

Note that that parameter doesn't mean you'll get an analyze every 500
rows.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Josh Berkus 2006-10-08 23:05:02 Re: Simple join optimized badly?
Previous Message Jim C. Nasby 2006-10-08 20:34:50 Re: Performance Optimization for Dummies 2 - the SQL