| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | sai(dot)dulla(at)berkeley(dot)edu |
| Subject: | BUG #15851: Concurrent Refresh of Materialized views not preserving the order of the underlying query |
| Date: | 2019-06-13 19:35:21 |
| Message-ID: | 15851-576ac1c22033d304@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 15851
Logged by: Sai D
Email address: sai(dot)dulla(at)berkeley(dot)edu
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-06-13 19:53:15 | Re: BUG #15844: MIPS: remove .set mips2 in s_lock.h to fix r6 build |
| Previous Message | Tom Lane | 2019-06-13 17:14:16 | Re: BUG #15847: Running out of memory when planning full outer joins involving many partitions |