Re: performance problem with LIMIT (order BY in DESC order). Wrong index used?

From: tv(at)fuzzy(dot)cz
To: "Claudio Freire" <klaussfreire(at)gmail(dot)com>
Cc: "Dieter Rehbein" <dieter(dot)rehbein(at)skiline(dot)cc>, pgsql-performance(at)postgresql(dot)org
Subject: Re: performance problem with LIMIT (order BY in DESC order). Wrong index used?
Date: 2011-04-12 09:33:31
Message-ID: 85b1e68e7ad292e4cae8fcfd8c8cb61a.squirrel@sq.gransy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> On Tue, Apr 12, 2011 at 10:59 AM, Dieter Rehbein
> <dieter(dot)rehbein(at)skiline(dot)cc> wrote:
>> I just executed a VACUUM ANALYZE and now everything performs well. hm,
>> strange.
>
> That probably means you need more statistics - try increasing the
> newsfeed's statistics target count.
>
> ALTER TABLE newsfeed_item ALTER COLUMN newsfeed SET STATISTICS <n>;
>
> Try different <n> numbers, you can crank it up to 4000 or perhaps more
> in 9.0, but you should start lower I guess.

AFAIK the max value is 10000 and the default is 100. Higher numbers mean
higher overhead, so do not jump to 10000 directly. Set it to 1000 and see
if that helps, etc.

regards
Tomas

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Dieter Rehbein 2011-04-12 09:36:23 Re: performance problem with LIMIT (order BY in DESC order). Wrong index used?
Previous Message Claudio Freire 2011-04-12 09:07:27 Re: performance problem with LIMIT (order BY in DESC order). Wrong index used?