Commit 6ccb2af7 authored by Tom Lane's avatar Tom Lane

Remove error report from pq_endmessage when pq_putmessage fails. The

only possible failure is in pq_flush, which will log a (better!) report
anyway --- so pq_endmessage is just cluttering the log with a redundant
entry.  This matters when a client crashes partway through a large query,
since we will emit many broken-pipe reports before finishing the query
and exiting.
parent c8e05aff
...@@ -16,7 +16,7 @@ ...@@ -16,7 +16,7 @@
* Portions Copyright (c) 1996-2001, PostgreSQL Global Development Group * Portions Copyright (c) 1996-2001, PostgreSQL Global Development Group
* Portions Copyright (c) 1994, Regents of the University of California * Portions Copyright (c) 1994, Regents of the University of California
* *
* $Id: pqformat.c,v 1.16 2001/01/24 19:42:56 momjian Exp $ * $Id: pqformat.c,v 1.17 2001/04/16 01:46:57 tgl Exp $
* *
*------------------------------------------------------------------------- *-------------------------------------------------------------------------
*/ */
...@@ -213,13 +213,8 @@ pq_sendint(StringInfo buf, int i, int b) ...@@ -213,13 +213,8 @@ pq_sendint(StringInfo buf, int i, int b)
void void
pq_endmessage(StringInfo buf) pq_endmessage(StringInfo buf)
{ {
if (pq_putmessage('\0', buf->data, buf->len)) (void) pq_putmessage('\0', buf->data, buf->len);
{ /* no need to complain about any failure, since pqcomm.c already did */
snprintf(PQerrormsg, PQERRORMSG_LENGTH,
"FATAL: pq_endmessage failed: errno=%d\n", errno);
fputs(PQerrormsg, stderr);
pqdebug("%s", PQerrormsg);
}
pfree(buf->data); pfree(buf->data);
buf->data = NULL; buf->data = NULL;
} }
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment