From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Allow for yet another crash symptom in 013_crash_restart.pl. |
Date: | 2019-01-27 03:12:58 |
Message-ID: | E1gnasU-0000Ul-NC@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Allow for yet another crash symptom in 013_crash_restart.pl.
Given the right timing, psql could emit "connection to server was lost"
rather than one of the other messages that this test script checked for.
It looks like commit 4247db625 may have made this more likely, but
I don't really believe it was impossible before then. Rather than
stress about it, just add that spelling as one of the crash-successfully-
detected cases.
Discussion: https://postgr.es/m/19344.1548554028@sss.pgh.pa.us
Branch
------
REL_11_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/04bbefcc30f0f41066607da319dea58e3a319433
Modified Files
--------------
src/test/recovery/t/013_crash_restart.pl | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2019-01-27 07:28:01 | Re: pgsql: Remove references to Majordomo |
Previous Message | Andres Freund | 2019-01-26 22:34:02 | pgsql: Change function call information to be variable length. |