Re: why do we need two snapshots per query?
От | Simon Riggs |
---|---|
Тема | Re: why do we need two snapshots per query? |
Дата | |
Msg-id | CA+U5nMK5pyOF3hTqz1qpW+-ELQbPHGmeM1LZVx_BtkkFJ8h5gQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: why do we need two snapshots per query? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: why do we need two snapshots per query?
|
Список | pgsql-hackers |
On Sun, Nov 13, 2011 at 4:09 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > As far as partitioning goes, the correct solution there > is to move the partition selection to run-time, so we should not be > contorting query semantics to make incremental performance improvements > with the existing partitioning infrastructure. Agreed, but I think we need both planning and execution time awareness, just as we do with indexonly. That's what I'd like to be able to do: link planning and execution. It's all very well to refuse individual cases where linkage is required, but ISTM clear that there are many possible uses of being able to tell whether a plan is one-shot or not and nothing lost by allowing that information (a boolean) pass to the executor. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: