pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Neil Conway <neilc@samurai.com>
Cc: Bruno Wolff III <bruno@wolff.to>
Cc: Keith Worthington <KeithW@NarrowPathInc.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: View vs function
Date: Mon, 21 Mar 2005 01:40:42 -0500
Message-ID: <11188.1111387242@sss.pgh.pa.us> (raw)
In-Reply-To: <423E57E5.4070405@samurai.com>
References: <423E420D.1020503@NarrowPathInc.com>
	<20050321042720.GA27098@wolff.to>
	<423E57E5.4070405@samurai.com>

Neil Conway <neilc@samurai.com> writes:
> Bruno Wolff III wrote:
>> Functions are just black boxes to the planner.

> ... unless the function is a SQL function that is trivial enough for the 
> planner to inline it into the plan of the invoking query. Currently, we 
> won't inline set-returning SQL functions that are used in the query's 
> rangetable, though. This would be worth doing, I think -- I'm not sure 
> how much work it would be, though.

Yeah, I've been thinking the same.  It seems like it shouldn't be unduly
difficult --- not harder than inlining scalar-valued SQL functions, just
different validity conditions.

			regards, tom lane



view thread (4+ messages)

Message-ID: <11188.1111387242@sss.pgh.pa.us>
Permalink:  ../11188.1111387242@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/11188.1111387242@sss.pgh.pa.us

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, neilc@samurai.com, bruno@wolff.to, KeithW@NarrowPathInc.com
  Subject: Re: View vs function
  In-Reply-To: <11188.1111387242@sss.pgh.pa.us>

* 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