Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Simple select hangs while CPU close to 100% - Analyze
- From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- To: Jozsef Szalay <jszalay(at)storediq(dot)com>
- Cc: Bill Moran <wmoran(at)collaborativefusion(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
- Subject: Re: Simple select hangs while CPU close to 100% - Analyze
- Date: Fri, 17 Aug 2007 23:03:49 -0400
Jozsef Szalay escribió: > I don't know why ANALYZE would have any effect on a sequential scan of a > table but it does appear to impact both performance and memory usage > significantly. It doesn't. What it does is provide the query optimizer with the information that it needs to know that the table contains many different values, which makes it turn the initial hashed aggregation into a sort plus group aggregation. This allows the aggregation to use less memory. As an exercise, see an EXPLAIN of the query, both before and after the analyze, and study the difference. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
- References:
- Re: Simple select hangs while CPU close to 100% - Analyze
- From: Jozsef Szalay
- Re: Simple select hangs while CPU close to 100% - Analyze
- Prev by Date: Re: select count(*) performance
- Next by Date: Re: Performance Solaris vs Linux
- Previous by thread: Re: Simple select hangs while CPU close to 100% - Analyze
- Next by thread: schema design question
- Indexes: