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

close at this point. Fix PQsetnonblocking() comment.

Fujii Masao
This commit is contained in:
Heikki Linnakangas 2011-03-30 08:54:28 +03:00
parent f564e65cda
commit bc03c5937d
2 changed files with 2 additions and 2 deletions

View File

@ -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)));
}
}

View File

@ -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.
*/