Re: Should total_pages be calculated after partition pruning and constraint exclusion?
От | Tom Lane |
---|---|
Тема | Re: Should total_pages be calculated after partition pruning and constraint exclusion? |
Дата | |
Msg-id | 28612.1526425454@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Should total_pages be calculated after partition pruning andconstraint exclusion? (David Rowley <david.rowley@2ndquadrant.com>) |
Ответы |
Re: Should total_pages be calculated after partition pruning andconstraint exclusion?
|
Список | pgsql-hackers |
David Rowley <david.rowley@2ndquadrant.com> writes: > On 16 May 2018 at 08:10, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> David Rowley <david.rowley@2ndquadrant.com> writes: >> Please add to next CF. It's a bit late to be doing such things in v11, >> IMO. > If I do that, it'll go under bug fix. No, it should go under "planner improvement". If this were a bug fix, it'd be a candidate for back-patch, which IMO it's not --- if only because of the risk of plan destabilization. But for a more direct analogy, if you'd submitted some other improvement in selectivity or cost estimation, that was not a bug fix in the sense of "corrects outright wrong answers", would you expect it to escape feature freeze at this point? Beta or no beta, there has to be a pretty good argument why changes should go into v11 and not v12 once we're past feature freeze. regards, tom lane
В списке pgsql-hackers по дате отправления: