| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Optimze usage of immutable functions as relation |
| Date: | 2019-07-26 18:40:35 |
| Message-ID: | 19453.1564166435@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> * It would be useful for the commentary to point out that in principle we
> could pull up any immutable (or, probably, even just stable) expression;
> but we don't, (a) for fear of multiple evaluations of the result costing
> us more than we can save, and (b) because a primary goal is to let the
> constant participate in further const-folding, and of course that won't
> happen for a non-Const.
BTW, so far as I can see, none of the test cases demonstrate that such
further const-folding can happen. Since this is all pretty processing-
order-sensitive, I think an explicit test that that's possible would
be a good idea.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-07-26 19:17:51 | Re: seems like a bug in pgbench -R |
| Previous Message | Tom Lane | 2019-07-26 18:26:00 | Re: Optimze usage of immutable functions as relation |