Adjust error message, now that we expect other message types than connection

hlinnaka · hlinnaka · commit bc03c5937d10 · 2011-03-30T08:54:28.000+03:00
close at this point. Fix PQsetnonblocking() comment.

Fujii Masao
diff --git 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
@@ -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.
  */

Original file line number	Diff line number	Diff line change
`@@ -506,7 +506,7 @@ ProcessRepliesIfAny(void)`
`506`	`506`	`default:`
`507`	`507`	`ereport(FATAL,`
`508`	`508`	`(errcode(ERRCODE_PROTOCOL_VIOLATION),`
`509`		`- errmsg("invalid standby closing message type %d",`
	`509`	`+ errmsg("invalid standby message type %d",`
`510`	`510`	`firstchar)));`
`511`	`511`	`}`
`512`	`512`	`}`