Re: Seeking help with a query that takes too long

From: Manfred Koizar <mkoi-pg(at)aon(dot)at>
To: <nickf(at)ontko(dot)com>
Cc: "Pgsql-Performance(at)Postgresql(dot) Org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Seeking help with a query that takes too long
Date: 2003-11-12 15:04:48
Message-ID: 03i4rv8cl6bgvr8r2c77ert3nfs0glfib8@email.aon.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, 12 Nov 2003 08:34:50 -0500, "Nick Fankhauser"
<nickf(at)ontko(dot)com> wrote:
> -> Index Scan using
>actor_full_name_uppercase on actor (cost=0.00..6.01 rows=1 width=42)
^^^^^^
>(actual time=37.62..677.44 rows=3501 loops=1)
^^^^^^^^^
> Index Cond:
>((actor_full_name_uppercase >= 'SANDERS'::character varying) AND
>(actor_full_name_uppercase < 'SANDERT'::character varying))
> Filter:
>(actor_full_name_uppercase ~~ 'SANDERS%'::text)

Nick, can you find out why this row count estimation is so far off?

\x
SELECT * FROM pg_stats
WHERE tablename='actor' AND attname='actor_full_name_uppercase';

BTW, there seem to be missing cases:
> -> Nested Loop (cost=0.00..2214.66 rows=2 width=115)
> (actual time=59.05..119929.71 rows=5879 loops=1)
^^^^
> -> Nested Loop (cost=0.00..2205.26 rows=3 width=76)
> (actual time=51.46..66089.04 rows=5882 loops=1)
^^^^

Servus
Manfred

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Rajesh Kumar Mallah 2003-11-12 15:04:53 Re: Suggestions for benchmarking 7.4RC2 against 7.3
Previous Message Rajesh Kumar Mallah 2003-11-12 14:47:26 Suggestions for benchmarking 7.4RC2 against 7.3