aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/commit_ts.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2017-09-22 11:29:05 -0700
committerAndres Freund <andres@anarazel.de>2017-09-22 11:35:26 -0700
commit8d926029e817d280b2376433e3aaa3895e1a7128 (patch)
treeb755f59f005b8471afd133e03c2214a90d55a28c /src/backend/access/transam/commit_ts.c
parentf9583e86b4bfa8c4e4d83ab33e5dcdaeab5c45a1 (diff)
downloadpostgresql-8d926029e817d280b2376433e3aaa3895e1a7128.tar.gz
postgresql-8d926029e817d280b2376433e3aaa3895e1a7128.zip
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
Diffstat (limited to 'src/backend/access/transam/commit_ts.c')
0 files changed, 0 insertions, 0 deletions