Skip to content

Commit cbadba8

Browse files
committed
Revert "Stabilize output of new regression test case".
This effectively reverts commit 9edc97b (although the test is now in a different place and has different contents). We don't need that hack anymore, because since commit 4b93f57, 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.
1 parent feb1cc5 commit cbadba8

File tree

2 files changed

+0
-4
lines changed

2 files changed

+0
-4
lines changed

src/pl/plpgsql/src/expected/plpgsql_varprops.out

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,6 @@ end$$;
176176
ERROR: null value cannot be assigned to variable "x" declared NOT NULL
177177
CONTEXT: PL/pgSQL function inline_code_block line 3 during statement block local variable initialization
178178
-- Check that variables are reinitialized on block re-entry.
179-
\set VERBOSITY terse \\ -- needed for output stability
180179
do $$
181180
begin
182181
for i in 1..3 loop
@@ -210,7 +209,6 @@ NOTICE: x = <NULL>
210209
NOTICE: y = 3
211210
NOTICE: r = <NULL>
212211
NOTICE: c = <NULL>
213-
\set VERBOSITY default
214212
-- Check enforcement of domain constraints during initialization
215213
do $$
216214
declare x int_nn; -- fail

src/pl/plpgsql/src/sql/plpgsql_varprops.sql

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -151,7 +151,6 @@ end$$;
151151

152152
-- Check that variables are reinitialized on block re-entry.
153153

154-
\set VERBOSITY terse \\ -- needed for output stability
155154
do $$
156155
begin
157156
for i in 1..3 loop
@@ -173,7 +172,6 @@ begin
173172
end;
174173
end loop;
175174
end$$;
176-
\set VERBOSITY default
177175

178176
-- Check enforcement of domain constraints during initialization
179177

0 commit comments

Comments
 (0)