From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Fix unstable regression test results. |
Date: | 2016-12-31 23:39:18 |
Message-ID: | [email protected] |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Fix unstable regression test results.
Commit 2ac3ef7a0 added a query with an underdetermined output row order;
it has failed multiple times in the buildfarm since then. Add an ORDER BY
to fix. Also, don't rely on a DROP CASCADE to drop in a well-determined
order; that hasn't failed yet but I don't trust it much, and we're not
saving any typing by using CASCADE anyway.
Branch
------
master
Modified Files
--------------
src/test/regress/expected/insert.out | 8 +++-----
src/test/regress/sql/insert.sql | 5 +++--
2 files changed, 6 insertions(+), 7 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2017-01-01 12:23:40 | Re: pgsql: Fix base backup rate limiting in presence of slow i/o |
Previous Message | Tom Lane | 2016-12-29 23:07:29 | pgsql: Fix incorrect example of to_timestamp() usage. |