From: Nick Fankhauser <nickf@ontko.com>
To: Manfred Koizar <mkoi-pg@aon.at>
To: Pgsql-Performance@Postgresql. Org <pgsql-performance@postgresql.org>
Subject: Re: Seeking help with a query that takes too long
Date: Wed, 12 Nov 2003 11:05:10 -0500
Message-ID: <NEBBLAAHGLEEPCGOBHDGCEJHJGAA.nickf@ontko.com> (raw)
In-Reply-To: <03i4rv8cl6bgvr8r2c77ert3nfs0glfib8@email.aon.at>
> >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)
> ^^^^^^^^^
> Nick, can you find out why this row count estimation is so far off?
^^^^^^^^^
Oops- I read this backward- I see what you mean now. That's a good question.
I'm not sure what part of the stats this estimate might be pulled from. The
average is 357, but the most common frequency may be around 1.
-Nick
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: nickf@ontko.com, mkoi-pg@aon.at
Subject: Re: Seeking help with a query that takes too long
In-Reply-To: <NEBBLAAHGLEEPCGOBHDGCEJHJGAA.nickf@ontko.com>
* 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