Commit8d92602

committed

Expand expected output for recovery test even further.

I'd assumed that the backend being killed should be able to get out anerror message - but it turns out it's not guaranteed that it's notstill sending a ready-for-query. Really need to do something aboutgetting these error message to the client.Reported-By: Thomas Munro, Tom LaneDiscussion:https://postgr.es/m/CAEepm=0TE90nded+bNthP45_PEvGAAr=3gxhHJObL4xmOLtX0w@mail.gmail.com https://postgr.es/m/14968.1506101414@sss.pgh.pa.us

1 parentf9583e8 commit8d92602Copy full SHA for 8d92602

File tree

-1

lines changed

-1

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -115,7 +115,7 @@`
`115`	`115`	`$killme_stdin .=q[`
`116`	`116`	`SELECT 1;`
`117`	`117`	`];`
`118`		`-ok(pump_until($killme, \$killme_stderr,qr/WARNING: terminating connection because of crash of another server process/m),`
	`118`	`+ok(pump_until($killme, \$killme_stderr,qr/WARNING: terminating connection because of crash of another server process\|server closed the connection unexpectedly/m),`
`119`	`119`	`"psql query died successfully after SIGQUIT");`
`120`	`120`	`$killme_stderr ='';`
`121`	`121`	`$killme_stdout ='';`

Comments

(0)