Re: Guide to PG's capabilities for inlining, predicate hoisting, flattening, etc?

Поиск
Список
Период
Сортировка
От Justin Pitts
Тема Re: Guide to PG's capabilities for inlining, predicate hoisting, flattening, etc?
Дата
Msg-id CAMYZu8UHu-zz3-2_C0vtdqwDiWMgsWQjuVPSvNYR5Sxuu-Me+g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Guide to PG's capabilities for inlining, predicate hoisting, flattening, etc?  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-performance
Дерево обсуждения
On Wed, Nov 2, 2011 at 11:13 AM, Robert Haas <robertmhaas@gmail.com> wrote:
[…]  Perhaps we could let people say
something like WITH x AS FENCE (...) when they want the fencing
behavior, and otherwise assume they don't (but give it to them anyway
if there's a data-modifying operation in there).

I would love to be able to test some of our CTE queries in such a scenario.

None of them do data modification. How hard would it be to patch my own build to disable the fence unilaterally for testing purposes? 

В списке pgsql-performance по дате отправления:

Предыдущее
От: Marti Raudsepp
Дата:
Сообщение: Re: SSL encryption makes bytea transfer slow
Следующее
От: Gavin Flower
Дата:
Сообщение: Re: Guide to PG's capabilities for inlining, predicate hoisting, flattening, etc?