Re: Suppressing unused subquery output columns

From: Jim Nasby <jim(at)nasby(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rod Taylor <rod(dot)taylor(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Suppressing unused subquery output columns
Date: 2014-06-06 21:37:25
Message-ID: 53923495.7010308@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6/5/14, 9:54 PM, Tom Lane wrote:
> Rod Taylor <rod(dot)taylor(at)gmail(dot)com> writes:
>> On Thu, Jun 5, 2014 at 10:27 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> I'm not entirely convinced that it's worth the extra planning cycles,
>>> though. Given the small number of complaints to date, it might not
>>> be worth doing this. Thoughts?
>
>> Would this avoid execution of expensive functions in views when their
>> output is discarded?
>
> Yes, as long as they're not marked volatile and don't return sets.

That would certainly make it useful for us.
--
Jim C. Nasby, Data Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2014-06-06 22:23:59 Re: Why is it "JSQuery"?
Previous Message Andres Freund 2014-06-06 19:58:28 Re: Inaccuracy in VACUUM's tuple count estimates