Re: avoid select expens_expr(col) like unneccessary calculations

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
Cc: Markus Bertheau <twanger(at)bluetwanger(dot)de>, pgsql-sql(at)postgresql(dot)org
Subject: Re: avoid select expens_expr(col) like unneccessary calculations
Date: 2003-07-21 15:23:36
Message-ID: 200307211523.h6LFNa112572@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Stephan Szabo wrote:
> On 8 Jul 2003, Markus Bertheau wrote:
>
> > when you have
> > select expensive_expression(column), * from table offset 20 limit 40
> >
> > can you somehow save the cost for the first 20 calculations of
> > expensive_expression?
>
> Right now the only way I can think of that might work is to push the
> offset/limit into a subselect on table and then do the
> expensive_expression at the top level.

Well, you can do:

SELECT * FROM (SELECT * FROM pg_class) AS pg_class

so you could do:

SELECT func(relname), *
FROM (SELECT * FROM pg_class OFFSET 20 LIMIT 40) AS pg_class

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Jean-Luc Lachance 2003-07-21 15:41:43 Re: min() and NaN
Previous Message Rod Taylor 2003-07-21 13:09:18 Re: Why their is a limit in Postgresql (psql) Parameters..?