From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Soon-to-be-broken regression test case |
Date: | 2018-10-11 20:45:44 |
Message-ID: | 23507.1539290744@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> writes:
> I guess if we ever did something to break that then we'd need to not
> do anything when there are volatile functions present.
Yeah, nothing I'm doing here changes the rule that we don't flatten
sub-selects containing volatiles in their tlist.
> If people are
> writing that then probably they're doing so to trick the planner,
> perhaps to hide some stats that get outdated easily. I'd imagine we'd
> upset more people than we'd please.
The specific case I'm aware of is that people sometimes write
"(SELECT x)" rather than just "x" so as to make the calculation
be a done-only-once InitPlan. That code path isn't affected by
this, either (and that's why the partition_prune tests didn't
change behavior).
It's fair to wonder whether partition_prune needs to be testing
other subplan cases besides InitPlans, but that seems like a
distinct issue.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Dolgov | 2018-10-11 20:49:04 | Re: [HACKERS] [PATCH] Generic type subscripting |
Previous Message | Christoph Berg | 2018-10-11 19:49:27 | Re: Debian mips: Failed test 'Check expected t_009_tbl data on standby' |