mirror of
https://github.com/postgres/postgres.git
synced 2025-05-21 15:54:08 +03:00
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:
parent
f564e65cda
commit
bc03c5937d
@ -506,7 +506,7 @@ ProcessRepliesIfAny(void)
|
|||||||
default:
|
default:
|
||||||
ereport(FATAL,
|
ereport(FATAL,
|
||||||
(errcode(ERRCODE_PROTOCOL_VIOLATION),
|
(errcode(ERRCODE_PROTOCOL_VIOLATION),
|
||||||
errmsg("invalid standby closing message type %d",
|
errmsg("invalid standby message type %d",
|
||||||
firstchar)));
|
firstchar)));
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
@ -2869,7 +2869,7 @@ PQparamtype(const PGresult *res, int param_num)
|
|||||||
|
|
||||||
/* PQsetnonblocking:
|
/* PQsetnonblocking:
|
||||||
* sets the PGconn's database connection non-blocking if the arg is TRUE
|
* 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.
|
* you from PQexec(), you'll only be safe when using the non-blocking API.
|
||||||
* Needs to be called only on a connected database connection.
|
* Needs to be called only on a connected database connection.
|
||||||
*/
|
*/
|
||||||
|
Loading…
x
Reference in New Issue
Block a user