Re: performance problem

From: Alvaro Herrera Munoz <alvherre(at)dcc(dot)uchile(dot)cl>
To: Rick Gigger <rick(at)alpinenetworking(dot)com>
Cc: Mike Mascari <mascarm(at)mascari(dot)com>, PgSQL General ML <pgsql-general(at)postgresql(dot)org>
Subject: Re: performance problem
Date: 2003-11-20 21:06:00
Message-ID: 20031120210600.GC26865@dcc.uchile.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

On Thu, Nov 20, 2003 at 01:52:10PM -0700, Rick Gigger wrote:

> I worked around this by starting the transaction and inserting the 45,000
> rows and then killing it. The I removed the index and readded it which
> apparently gathered some stats and since there were all of the dead tuples
> in there from the failed transaction it now decided that it should use the
> index. I reran the script and this time it took 5 minutes again instead of
> 1 1/2 hours.

Stats are not collected automatically. You should run ANALYZE after
importing your data. And it's probably faster to create the index after
the data is loaded, too.

--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
Y una voz del caos me habl y me dijo
"Sonre y s feliz, podra ser peor".
Y sonre. Y fui feliz.
Y fue peor.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Rick Gigger 2003-11-20 21:07:43 Re: performance problem
Previous Message fred 2003-11-20 20:59:10 Re: performance problem

Browse pgsql-general by date

  From Date Subject
Next Message Rick Gigger 2003-11-20 21:07:43 Re: performance problem
Previous Message Tom Lane 2003-11-20 21:04:11 Re: ERROR: nodeRead: did not find '}' [x2]