From df9f348a8ac7d931d230e4021c81ae7afa4ecfaf Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Wed, 21 Jan 2015 22:01:16 +0200 Subject: [PATCH] Silence regression failure of diagnostic test. Now that I fixed the bug in the error handler, we're not losing the libpq's message about lost connect anymore. It overwrites the previous FATAL error, which is unfortunate, but it's been long-standing behaviour that if multiple errors are returned as result for a query, only the last one is kept. --- test/expected/diagnostic.out | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/test/expected/diagnostic.out b/test/expected/diagnostic.out index ef99e47..05f31cb 100644 --- a/test/expected/diagnostic.out +++ b/test/expected/diagnostic.out @@ -7,9 +7,18 @@ get same message again 42601=ERROR: syntax error at or near "broken"; Error while executing the query killing connection... -57P01=FATAL: terminating connection due to administrator command; +57P01=server closed the connection unexpectedly + This probably means the server terminated abnormally + before or while processing the request. +; Error while executing the query SQLGetDiagRec on connection says: -57P01=FATAL: terminating connection due to administrator command +57P01=server closed the connection unexpectedly + This probably means the server terminated abnormally + before or while processing the request. + SQLGetDiagRec called again: -57P01=FATAL: terminating connection due to administrator command +57P01=server closed the connection unexpectedly + This probably means the server terminated abnormally + before or while processing the request. + -- 2.39.5