diff options
| author | Andres Freund | 2017-09-22 18:29:05 +0000 |
|---|---|---|
| committer | Andres Freund | 2017-09-22 18:35:26 +0000 |
| commit | 8d926029e817d280b2376433e3aaa3895e1a7128 (patch) | |
| tree | b755f59f005b8471afd133e03c2214a90d55a28c | |
| parent | f9583e86b4bfa8c4e4d83ab33e5dcdaeab5c45a1 (diff) | |
Expand expected output for recovery test even further.
I'd assumed that the backend being killed should be able to get out an
error message - but it turns out it's not guaranteed that it's not
still sending a ready-for-query. Really need to do something about
getting these error message to the client.
Reported-By: Thomas Munro, Tom Lane
Discussion:
https://postgr.es/m/CAEepm=0TE90nded+bNthP45_PEvGAAr=3gxhHJObL4xmOLtX0w@mail.gmail.com
https://postgr.es/m/14968.1506101414@sss.pgh.pa.us
| -rw-r--r-- | src/test/recovery/t/013_crash_restart.pl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/recovery/t/013_crash_restart.pl b/src/test/recovery/t/013_crash_restart.pl index 23024716e6d..ce35bdd6338 100644 --- a/src/test/recovery/t/013_crash_restart.pl +++ b/src/test/recovery/t/013_crash_restart.pl @@ -115,7 +115,7 @@ is($cnt, 1, "exactly one process killed with SIGQUIT"); $killme_stdin .= q[ SELECT 1; ]; -ok(pump_until($killme, \$killme_stderr, qr/WARNING: terminating connection because of crash of another server process/m), +ok(pump_until($killme, \$killme_stderr, qr/WARNING: terminating connection because of crash of another server process|server closed the connection unexpectedly/m), "psql query died successfully after SIGQUIT"); $killme_stderr = ''; $killme_stdout = ''; |