Re: BUG #10194: Stable function in select clause cann't be optimized to one call?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: digoal(at)126(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #10194: Stable function in select clause cann't be optimized to one call?
Date: 2014-05-01 19:37:16
Message-ID: 4618.1398973036@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

digoal(at)126(dot)com writes:
> Why stable function in select clause cann't optimized to one time call?

Because its value might change between planning and execution.

There was some discussion awhile back of performing run-time caching of
the result, but it isn't done yet, and would impose some costs of its own.

BTW, this sort of question is not a bug.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message 德哥 2014-05-02 00:13:49 Re: BUG #10194: Stable function in select clause cann't be optimized to one call?
Previous Message digoal 2014-05-01 09:09:04 BUG #10194: Stable function in select clause cann't be optimized to one call?