diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-02-29 19:29:19 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-02-29 19:29:19 -0500 |
| commit | 3d523564c53ab8f35edf4d20627f0a375a17624d (patch) | |
| tree | 611e04874b128a50154ed5388fe34d49ee9eb047 /src | |
| parent | 8d8ff5f7db7d58240fac7d5f620308c91485b253 (diff) | |
| download | postgresql-3d523564c53ab8f35edf4d20627f0a375a17624d.tar.gz postgresql-3d523564c53ab8f35edf4d20627f0a375a17624d.zip | |
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.
Diffstat (limited to 'src')
| -rw-r--r-- | src/test/isolation/specs/async-notify.spec | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/isolation/specs/async-notify.spec b/src/test/isolation/specs/async-notify.spec index 7f451b18a15..8adad42c7c8 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; } |