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

Commit 3d52356

Browse files
committed
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.
1 parent 8d8ff5f commit 3d52356

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/test/isolation/specs/async-notify.spec

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
session "listener"
66
step "listen" { LISTEN a; }
77
step "begin" { BEGIN; }
8-
teardown { ROLLBACK; }
8+
teardown { ROLLBACK; UNLISTEN *; }
99

1010
session "notifier"
1111
step "check" { SELECT pg_notification_queue_usage() > 0 AS nonzero; }

0 commit comments

Comments
 (0)