database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-06 19:59:18 +03:00
Code

Suppress DETAIL output from an event_trigger test.

Browse Source 
Suppress 3 lines of unstable DETAIL output from a DROP ROLE statement in
event_trigger.sql.  This is further cleanup for commit dd299df8.

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 dd299df8.

Per buildfarm member macaque.
This commit is contained in:
Peter Geoghegan 2019-03-23 13:49:53 -07:00
parent 29b64d1de7
commit 05f110cc0b
2 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/test/regress/expected/event_trigger.out
View File

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

3
src/test/regress/sql/event_trigger.sql
View File

@ -157,7 +157,10 @@ alter event trigger regress_event_trigger rename to regress_event_trigger3;
drop event trigger regress_event_trigger; drop event trigger regress_event_trigger;
-- should fail, regress_evt_user owns some objects -- should fail, regress_evt_user owns some objects
-- use terse mode to avoid ordering issues in DROP ROLE detail output
\set VERBOSITY terse
drop role regress_evt_user; drop role regress_evt_user;
\set VERBOSITY default
-- cleanup before next test -- cleanup before next test
-- these are all OK; the second one should emit a NOTICE -- these are all OK; the second one should emit a NOTICE