PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID15851
PG Version10.5
OSUbuntu 16.04.10
Opened2019-06-13 19:35:21+00
Reported bySai D
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      15851
Logged by:          Sai D
Email address:      (redacted)
PostgreSQL version: 10.5
Operating system:   Ubuntu 16.04.10
Description:        

Tests Run:
Materialized view refresh concurrently with unique index: 
Sort order is not the same as that of the output of the underlying query

Tested with Unique Index key that is the same as the sort order columns in
the underlying query. 
Results: Incorrect sort order after refresh concurrently
Tested with Unique Index key that is different from the sort order columns
in the underlying query. 
Results: Incorrect sort order after refresh concurrently


Materialized view refresh with unique index (Plain refresh, no concurrently
key word in the refresh command): 
Sort order is the same as that of the output of the underlying query

Messages

DateAuthorSubject
2019-06-13 19:35:21+00PG Bug reporting formBUG #15851: Concurrent Refresh of Materialized views not preserving the order of the underlying query
2019-06-14 00:28:54+00Tom LaneRe: BUG #15851: Concurrent Refresh of Materialized views not preserving the order of the underlying query
2019-06-14 00:47:10+00"David G(dot) Johnston"BUG #15851: Concurrent Refresh of Materialized views not preserving the order of the underlying query
2019-06-14 01:17:22+00David RowleyRe: BUG #15851: Concurrent Refresh of Materialized views not preserving the order of the underlying query
2019-06-17 16:48:39+00Andres FreundRe: BUG #15851: Concurrent Refresh of Materialized views not preserving the order of the underlying query