pgsql: Avoid use of DROP TABLE .. CASCADE in partitioning tests.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Avoid use of DROP TABLE .. CASCADE in partitioning tests.
Date: 2017-01-18 19:57:54
Message-ID: E1cTwMk-0005tO-Vi@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Avoid use of DROP TABLE .. CASCADE in partitioning tests.

This isn't really guaranteed to always produce exactly the same
output; the order can change from run to run.

See related cleanup in 257d8157205a7be5f9799e8941b922521d678a25.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/e509e7f9e3c565043e1186f5a83122d71653d111

Modified Files
--------------
src/test/regress/expected/insert.out | 26 ++++----------------------
src/test/regress/sql/insert.sql | 6 ++++--
2 files changed, 8 insertions(+), 24 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-01-18 20:22:18 pgsql: Disable transforms that replaced AT TIME ZONE with RelabelType.
Previous Message Robert Haas 2017-01-18 19:48:15 pgsql: Add some more tests for tuple routing.