Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 05f110c

Browse files
Suppress DETAIL output from an event_trigger test.
Suppress 3 lines of unstable DETAIL output from a DROP ROLE statement in event_trigger.sql. This is further cleanup for commit dd299df. Note that the event_trigger test instability issue is very similar to the recently suppressed foreign_data test instability issue. Both issues involve DETAIL output for a DROP ROLE statement that needed to be changed as part of dd299df. Per buildfarm member macaque.
1 parent 29b64d1 commit 05f110c

File tree

2 files changed

+6
-3
lines changed

2 files changed

+6
-3
lines changed

src/test/regress/expected/event_trigger.out

+3-3
Original file line numberDiff line numberDiff line change
@@ -185,11 +185,11 @@ alter event trigger regress_event_trigger rename to regress_event_trigger3;
185185
drop event trigger regress_event_trigger;
186186
ERROR: event trigger "regress_event_trigger" does not exist
187187
-- should fail, regress_evt_user owns some objects
188+
-- use terse mode to avoid ordering issues in DROP ROLE detail output
189+
\set VERBOSITY terse
188190
drop role regress_evt_user;
189191
ERROR: role "regress_evt_user" cannot be dropped because some objects depend on it
190-
DETAIL: owner of user mapping for regress_evt_user on server useless_server
191-
owner of default privileges on new relations belonging to role regress_evt_user
192-
owner of event trigger regress_event_trigger3
192+
\set VERBOSITY default
193193
-- cleanup before next test
194194
-- these are all OK; the second one should emit a NOTICE
195195
drop event trigger if exists regress_event_trigger2;

src/test/regress/sql/event_trigger.sql

+3
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,10 @@ alter event trigger regress_event_trigger rename to regress_event_trigger3;
157157
drop event trigger regress_event_trigger;
158158

159159
-- should fail, regress_evt_user owns some objects
160+
-- use terse mode to avoid ordering issues in DROP ROLE detail output
161+
\set VERBOSITY terse
160162
drop role regress_evt_user;
163+
\set VERBOSITY default
161164

162165
-- cleanup before next test
163166
-- these are all OK; the second one should emit a NOTICE

0 commit comments

Comments
 (0)