From: Heikki Linnakangas <heikki.linnakangas@iki.fi>
Date: Wed, 30 Mar 2011 05:54:28 +0000 (+0300)
Subject: Adjust error message, now that we expect other message types than connection
X-Git-Tag: REL9_1_BETA1~189
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=bc03c5937d103952ef4f40a3fa4514c154538d25;p=postgresql

Adjust error message, now that we expect other message types than connection
close at this point. Fix PQsetnonblocking() comment.

Fujii Masao
---

diff --git a/src/backend/replication/walsender.c b/src/backend/replication/walsender.c
index f76b5b081d..2e2659a8c9 100644
--- a/src/backend/replication/walsender.c
+++ b/src/backend/replication/walsender.c
@@ -506,7 +506,7 @@ ProcessRepliesIfAny(void)
 			default:
 				ereport(FATAL,
 						(errcode(ERRCODE_PROTOCOL_VIOLATION),
-						 errmsg("invalid standby closing message type %d",
+						 errmsg("invalid standby message type %d",
 								firstchar)));
 		}
 	}
diff --git a/src/interfaces/libpq/fe-exec.c b/src/interfaces/libpq/fe-exec.c
index dcdb1a9351..42da1a8f90 100644
--- a/src/interfaces/libpq/fe-exec.c
+++ b/src/interfaces/libpq/fe-exec.c
@@ -2869,7 +2869,7 @@ PQparamtype(const PGresult *res, int param_num)
 
 /* PQsetnonblocking:
  *	sets the PGconn's database connection non-blocking if the arg is TRUE
- *	or makes it non-blocking if the arg is FALSE, this will not protect
+ *	or makes it blocking if the arg is FALSE, this will not protect
  *	you from PQexec(), you'll only be safe when using the non-blocking API.
  *	Needs to be called only on a connected database connection.
  */