From 3d523564c53ab8f35edf4d20627f0a375a17624d Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 29 Feb 2016 19:29:19 -0500 Subject: [PATCH] Suppress scary-looking log messages from async-notify isolation test. I noticed that the async-notify test results in log messages like these: LOG: could not send data to client: Broken pipe FATAL: connection to client lost This is because it unceremoniously disconnects a client session that is about to have some NOTIFY messages delivered to it. Such log messages during a regression test might well cause people to go looking for a problem that doesn't really exist (it did cause me to waste some time that way). We can shut it up by adding an UNLISTEN command to session teardown. Patch HEAD only; this doesn't seem significant enough to back-patch. --- src/test/isolation/specs/async-notify.spec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/test/isolation/specs/async-notify.spec b/src/test/isolation/specs/async-notify.spec index 7f451b18a1..8adad42c7c 100644 --- a/src/test/isolation/specs/async-notify.spec +++ b/src/test/isolation/specs/async-notify.spec @@ -5,7 +5,7 @@ session "listener" step "listen" { LISTEN a; } step "begin" { BEGIN; } -teardown { ROLLBACK; } +teardown { ROLLBACK; UNLISTEN *; } session "notifier" step "check" { SELECT pg_notification_queue_usage() > 0 AS nonzero; } -- GitLab