pgsql: Use ORDER BY on matview definitions were needed for stable plans

From: Kevin Grittner <kgrittn(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use ORDER BY on matview definitions were needed for stable plans
Date: 2013-03-19 15:35:05
Message-ID: E1UHyZ7-0000FJ-Fo@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Use ORDER BY on matview definitions were needed for stable plans.

Per report from Hadi Moshayedi of matview regression test failure
with optimization of aggregates. A few ORDER BY clauses improve
code coverage for matviews while solving that problem.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/241139ae4baf6264c3c2cd053a547833c6e49a59

Modified Files
--------------
src/test/regress/expected/matview.out | 35 ++++++++++++++++++--------------
src/test/regress/sql/matview.sql | 8 +++---
2 files changed, 24 insertions(+), 19 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2013-03-20 17:54:22 pgsql: Bump up timeout delays some more in timeouts isolation test.
Previous Message Simon Riggs 2013-03-19 08:58:48 pgsql: Clarify assumption of filesystem metadata integrity.