pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: nickf@ontko.com
Cc: Manfred Koizar <mkoi-pg@aon.at>
Cc: Pgsql-Performance@Postgresql. Org <pgsql-performance@postgresql.org>
Subject: Re: Seeking help with a query that takes too long
Date: Wed, 12 Nov 2003 12:10:35 -0500
Message-ID: <10144.1068657035@sss.pgh.pa.us> (raw)
In-Reply-To: <NEBBLAAHGLEEPCGOBHDGMEJKJGAA.nickf@ontko.com>
References: <NEBBLAAHGLEEPCGOBHDGMEJKJGAA.nickf@ontko.com>

"Nick Fankhauser" <nickf@ontko.com> writes:
> This indicates to me that 1 isn't too shabby as an estimate if the whole
> name is specified, but I'm not sure how this gets altered in the case of a
> "LIKE"

For a pattern like "SANDERS%", the estimate is basically a range estimate
for this condition:

> ((actor_full_name_uppercase >= 'SANDERS'::character varying) AND
> (actor_full_name_uppercase < 'SANDERT'::character varying))

> n_distinct        | -0.14701

> Question: What does it mean when n_distinct is negative?

It means that the number of distinct values is estimated as a fraction
of the table size, rather than an absolute number.  In this case 14.7%
of the table size, which is a bit off compared to the correct value
of 43% (1453371/3386359), but at least it's of the right order of
magnitude now ...

>                                        ->  Index Scan using
> actor_full_name_uppercase on actor  (cost=0.00..456.88 rows=113 width=42)
> (actual time=32.80..3197.28 rows=3501 loops=1)

Hmm.  Better, but not enough better to force a different plan choice.

You might have to resort to brute force, like "set enable_nestloop=false".
Just out of curiosity, what do you get if you do that?

			regards, tom lane



view thread (11+ messages)  latest in thread

Message-ID: <10144.1068657035@sss.pgh.pa.us>
Permalink:  ../10144.1068657035@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/10144.1068657035@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, nickf@ontko.com, mkoi-pg@aon.at
  Subject: Re: Seeking help with a query that takes too long
  In-Reply-To: <10144.1068657035@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox