Re: performance problem
Alvaro Herrera <alvherre@dcc.uchile.cl>
From: Alvaro Herrera Munoz <alvherre@dcc.uchile.cl>
To: Rick Gigger <rick@alpinenetworking.com>
Cc: Mike Mascari <mascarm@mascari.com>, PgSQL General ML <pgsql-general@postgresql.org>
Date: 2003-11-20T21:06:00Z
Lists: 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[@]dcc.uchile.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.