forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit3d52356
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 pipeFATAL: connection to client lostThis is because it unceremoniously disconnects a client session that isabout to have some NOTIFY messages delivered to it. Such log messagesduring a regression test might well cause people to go looking for aproblem that doesn't really exist (it did cause me to waste some time thatway). 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 parent8d8ff5f commit3d52356
1 file changed
+1
-1
lines changedLines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
5 | 5 | | |
6 | 6 | | |
7 | 7 | | |
8 | | - | |
| 8 | + | |
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
| |||
0 commit comments
Comments
(0)