| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Revert "Stabilize output of new regression test case". |
| Date: | 2018-02-14 23:42:21 |
| Message-ID: | E1em6gv-0004Wx-9t@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Revert "Stabilize output of new regression test case".
This effectively reverts commit 9edc97b71 (although the test is now
in a different place and has different contents). We don't need that
hack anymore, because since commit 4b93f5799, this test case no longer
throws an error and so there's no displayed CONTEXT that could vary
depending on CLOBBER_CACHE_ALWAYS. The underlying unstable-output
problem isn't really gone, of course, but it no longer manifests here.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/cbadba8dd632fc0d4162f7d686fec631bce7dfd0
Modified Files
--------------
src/pl/plpgsql/src/expected/plpgsql_varprops.out | 2 --
src/pl/plpgsql/src/sql/plpgsql_varprops.sql | 2 --
2 files changed, 4 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-02-15 00:43:54 | pgsql: Move the extern declaration for ExceptionalCondition into c.h. |
| Previous Message | Tom Lane | 2018-02-14 23:18:14 | pgsql: Stabilize new plpgsql_record regression tests. |