Re: BUG #15851: Concurrent Refresh of Materialized views notpreserving the order of the underlying query

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: BUG #15851: Concurrent Refresh of Materialized views notpreserving the order of the underlying query
Дата
Msg-id CAKJS1f9z0o6zxJ7=Au6K4kxVigkn_G6XC2NKtWB_YQAT0_qjSw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #15851: Concurrent Refresh of Materialized views not preserving the order of the underlying query  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Дерево обсуждения 
On Fri, 14 Jun 2019 at 12:29, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> A more aggressive approach would be to reject ORDER BY in the
> query defining a matview, but perhaps that's too in-your-face...

Yeah. I think if we'd thought about it at the time we'd probably have
rejected an ORDER BY in the view definition. Doing that today might
break pg_upgrade and pg_restore.  Do you think there's any merit in a
WARNING during CREATE MATERIALIZED VIEW if the query has an ORDER BY?

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

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

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: BUG #15851: Concurrent Refresh of Materialized views not preservingthe order of the underlying query
Следующее
От: Feike Steenbergen
Дата:
Сообщение: Re: BUG #15847: Running out of memory when planning full outer joinsinvolving many partitions