Skip site navigation (1) Skip section navigation (2)

Re: Performance Anomaly with "col in (A,B)" vs. "col = A OR col = B" ver. 9.0.3

From: Craig James <craig_james(at)emolecules(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Performance Anomaly with "col in (A,B)" vs. "col = A OR col = B" ver. 9.0.3
Date: 2011-09-26 17:18:49
Message-ID: 4E80B3F9.8070001@emolecules.com (view raw or flat)
Thread:
Lists: pgsql-performance
On 9/26/11 10:07 AM, Tom Lane wrote:
> Cranking up the statistics target for the hts_code_id column (and re-ANALYZEing) ought to fix it. If all your tables are this large you might want to just increase default_statistics_target across the board. regards, tom lane 
This is common advice in this forum ....  but what's the down side to increasing statistics?  With so many questions coming to this forum that are due to insufficient statistics, why not just increase the default_statistics_target?  I assume there is a down side, but I've never seen it discussed.  Does it increase planning time?  Analyze time?  Take lots of space?

Thanks,
Craig

In response to

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2011-09-26 17:35:11
Subject: Re: Performance Anomaly with "col in (A,B)" vs. "col = A OR col = B" ver. 9.0.3
Previous:From: Tom LaneDate: 2011-09-26 17:07:51
Subject: Re: Performance Anomaly with "col in (A,B)" vs. "col = A OR col = B" ver. 9.0.3

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group