pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hannu Krosing <hannu@tm.ee>
To: Frederic Jolliton <fred-pg@jolliton.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Important speed difference between a query and a
Date: 25 Apr 2003 10:01:31 +0300
Message-ID: <1051254090.2997.3.camel@fuji.krosing.net> (raw)
In-Reply-To: <86bryvsvmo.fsf@mau.localdomain>
References: <8665p56qx8.fsf@mau.localdomain>
	<86el3rsxqu.fsf@mau.localdomain>
	<14131.1051199816@sss.pgh.pa.us>
	<86bryvsvmo.fsf@mau.localdomain>

Frederic Jolliton kirjutas N, 24.04.2003 kell 19:33:
> > Frederic Jolliton <fred-pg@jolliton.com> writes:
> >>> To "emulate" a parametred view, I created a function as follow:
> >>> 
> >>> CREATE FUNCTION get_info (integer) RETURNS SETOF type_get_info
> >>> AS '...' <- here the query show below, where 'LIMIT $1' is used instead of 'LIMIT 10'
> >>> LANGUAGE sql;
> >
> >> So, the query in the function is not using index but the exact same
> >> query alone does !
> 
> Tom Lane <tgl@sss.pgh.pa.us> writes:
> > But it's not the same query, is it?  With "LIMIT $1" the planner can't
> > know what the limit value is exactly, so it has to generate a plan that
> > won't be too unreasonable for either a small or a large limit.
> 
> Ok. So the query is optimized once and not each time.. I understand
> now.
> 
> But, since I "know" better that PostgreSQL that query must use index
> in most of case, can I force in some manner the function when
> declaring it to take this in account ? 

You could define two functions - one for small sets with constant LIMITs
(maybe 50) in UNION parts, and another with $1. Then use accordingly.

> I suppose (not tested) that
> setting enable_seqscan just before will probably do it, but what about
> dump/restore of the database when recreating the function and keep
> this "fix" automatically ?

-------------
Hannu




view thread (10+ messages)  latest in thread

Message-ID: <1051254090.2997.3.camel@fuji.krosing.net>
Permalink:  ../1051254090.2997.3.camel@fuji.krosing.net/
Also on:    postgresql.org/message-id/1051254090.2997.3.camel@fuji.krosing.net

 · 

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: hannu@tm.ee, fred-pg@jolliton.com
  Subject: Re: Important speed difference between a query and a
  In-Reply-To: <1051254090.2997.3.camel@fuji.krosing.net>
  References: <8665p56qx8.fsf@mau.localdomain> <86el3rsxqu.fsf@mau.localdomain> <14131.1051199816@sss.pgh.pa.us> <86bryvsvmo.fsf@mau.localdomain> <1051254090.2997.3.camel@fuji.krosing.net>

* 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