aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/complex.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-01-26 22:12:49 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2019-01-26 22:12:49 -0500
commit04bbefcc30f0f41066607da319dea58e3a319433 (patch)
tree64a2a2fe111edb1086b783861e92e136b0641311 /src/tutorial/complex.c
parent2c50c9f23d1dbb36b4fed50409ec590a0e9adaa2 (diff)
downloadpostgresql-04bbefcc30f0f41066607da319dea58e3a319433.tar.gz
postgresql-04bbefcc30f0f41066607da319dea58e3a319433.zip
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
Diffstat (limited to 'src/tutorial/complex.c')
0 files changed, 0 insertions, 0 deletions