From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Go back to suppressing foreign_data DETAIL test output. |
Date: | 2019-03-22 18:37:00 |
Message-ID: | E1h7P2K-0002JF-9D@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Go back to suppressing foreign_data DETAIL test output.
This is almost a straight revert of commit fff518d, which itself was a
revert of 7d3bf73ac.
It turns out that commit 8aa9dd74, which sorted dependent objects before
deletion in DROP OWNED BY, was not sufficient to make all remaining
unstable DETAIL output stable. Unstable DETAIL output from DROP ROLE
was not affected, because that happens to use a different code path. It
doesn't seem worthwhile to fix the other code path at this time.
Discussion: https://postgr.es/m/6226.1553274783@sss.pgh.pa.us
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/09963cedced7ffb98a06298cc16305767fd2b4dd
Modified Files
--------------
src/test/regress/expected/foreign_data.out | 6 +++---
src/test/regress/sql/foreign_data.sql | 4 +++-
2 files changed, 6 insertions(+), 4 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-03-22 18:56:26 | pgsql: Rearrange make_partitionedrel_pruneinfo to avoid work when we ca |
Previous Message | Tom Lane | 2019-03-22 18:17:17 | pgsql: Don't copy PartitionBoundInfo in set_relation_partition_info. |