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 f76b5b0..2e2659a 100644 (file)
--- 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 dcdb1a9..42da1a8 100644 (file)
--- 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.
  */