Re: BUG #8606: Materialized View WITH NO DATA bug
От | Tom Lane |
---|---|
Тема | Re: BUG #8606: Materialized View WITH NO DATA bug |
Дата | |
Msg-id | 31136.1384919378@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #8606: Materialized View WITH NO DATA bug (Kevin Grittner <kgrittn@ymail.com>) |
Ответы |
Re: BUG #8606: Materialized View WITH NO DATA bug
Re: BUG #8606: Materialized View WITH NO DATA bug |
Список | pgsql-bugs |
Kevin Grittner <kgrittn@ymail.com> writes: > "j.rejda@konektel.cz" <j.rejda@konektel.cz> wrote: >> -- this returns "after some time" (as long as normal "SELECT >> long_test(10);" >> do) >> CREATE MATERIALIZED VIEW test2 AS >> SELECT long_test(10) WITH NO DATA; >> >> -- it's ok or bug? > It's not a bug in the sense that it crashes or returns an incorrect > result, but it may be an opportunity for a performance enhancement. Meh. I'm not sure this can be considered to be a problem. One of the implications of marking a function immutable is that it has no side-effects worthy of concern; otherwise, it wouldn't be safe for the planner to constant-fold it, which is pretty much the whole point of immutability. But if you're concerned about how long it takes to evaluate, that's a kind of side effect, IMHO. Maybe it'd be better if you marked the function VOLATILE. But having said that, it seems that this complaint implies that CREATE MATERIALIZED VIEW ... WITH NO DATA still runs the query through a planning cycle. Why is that? I can't immediately see any benefit to doing so. regards, tom lane
В списке pgsql-bugs по дате отправления: