Re: BUG #15851: Concurrent Refresh of Materialized views notpreserving the order of the underlying query - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #15851: Concurrent Refresh of Materialized views notpreserving the order of the underlying query
Date
Msg-id 20190617164839.ypjeuytjvjp7ezo5@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #15851: Concurrent Refresh of Materialized views not preserving the order of the underlying query  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi,

On 2019-06-13 20:28:54 -0400, Tom Lane 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...

That'd probably be over the top - ISTM it can make plenty of sense to
"pre order" a matview, especially if you're going to create several
indexes.

Greetings,

Andres Freund



pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #15844: MIPS: remove .set mips2 in s_lock.h to fix r6 build
Next
From: Tom Lane
Date:
Subject: Re: BUG #15844: MIPS: remove .set mips2 in s_lock.h to fix r6 build