X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id DE558B4316B for ; Mon, 7 Jul 2003 23:03:08 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 65124-01 for ; Mon, 7 Jul 2003 20:02:58 -0300 (ADT) Received: from mail1.ihs.com (mail1.ihs.com [170.207.70.222]) by svr1.postgresql.org (Postfix) with ESMTP id 7414EB430D6 for ; Mon, 7 Jul 2003 20:02:57 -0300 (ADT) Received: from css120.ihs.com (css120.ihs.com [170.207.105.120]) by mail1.ihs.com (8.12.9/8.12.9) with ESMTP id h67N2Mv5004420; Mon, 7 Jul 2003 17:02:22 -0600 (MDT) Date: Mon, 7 Jul 2003 16:55:53 -0600 (MDT) From: "scott.marlowe" To: Markus Bertheau Cc: Subject: Re: avoid select expens_expr(col) like unneccessary calculations In-Reply-To: <1057617306.2617.6.camel@saphir> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner: Found to be clean X-MailScanner-SpamCheck: X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/82 X-Sequence-Number: 14196 On 8 Jul 2003, Markus Bertheau wrote: > Hi, > > 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? Might a functional or partial index work here?