pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Giorgio Valoti <giorgio_v@mac.com>
To: pgsql-performance@postgresql.org
Subject: Re: Query Plan choice with timestamps
Date: Fri, 08 Aug 2008 07:38:10 +0200
Message-ID: <3CA742D3-1D67-4572-AD4A-F7AA479771C7@mac.com> (raw)
In-Reply-To: <27578.1218142907@sss.pgh.pa.us>
References: <321506D5-4400-470C-909E-C7700D49A540@mac.com>
	<12707.1218124259@sss.pgh.pa.us>
	<A7C0E4E0-460D-49AB-912B-050E8049B16D@mac.com>
	<27578.1218142907@sss.pgh.pa.us>


On 07/ago/08, at 23:01, Tom Lane wrote:

> Giorgio Valoti <giorgio_v@mac.com> writes:
>> On 07/ago/08, at 17:50, Tom Lane wrote:
>>> These numbers seem pretty bogus: there is hardly any scenario in
>>> which a
>>> full-table indexscan should be costed as significantly cheaper  
>>> than a
>>> seqscan.  Have you put in silly values for random_page_cost?
>
>> No,
>
> I looked at it more closely and realized that the cost discrepancy is
> from the evaluation of the function: having to evaluate a SQL or  
> plpgsql
> function 247736 times more than explains the cost estimate  
> differential
> compared to a query that involves no function call.  Some experiments
> here suggest that it hardly matters whether the query uses indexscan  
> or
> seqscan because the time is dominated by the function calls anyway.

I see, thank you Tom. Could it be a good idea adding some notes about  
it in <http://www.postgresql.org/docs/8.3/interactive/indexes-expressional.html 
 >? As you said, since the function call dominates the query cost, in  
this case, I think there’s no point to use an index expression.

Ciao
--
Giorgio Valoti


view thread (10+ messages)

Message-ID: <3CA742D3-1D67-4572-AD4A-F7AA479771C7@mac.com>
Permalink:  ../3CA742D3-1D67-4572-AD4A-F7AA479771C7@mac.com/
Also on:    postgresql.org/message-id/3CA742D3-1D67-4572-AD4A-F7AA479771C7@mac.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: giorgio_v@mac.com
  Subject: Re: Query Plan choice with timestamps
  In-Reply-To: <3CA742D3-1D67-4572-AD4A-F7AA479771C7@mac.com>
  References: <321506D5-4400-470C-909E-C7700D49A540@mac.com> <12707.1218124259@sss.pgh.pa.us> <A7C0E4E0-460D-49AB-912B-050E8049B16D@mac.com> <27578.1218142907@sss.pgh.pa.us> <3CA742D3-1D67-4572-AD4A-F7AA479771C7@mac.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