c8h4/postgresql
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

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

Browse source 
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
Show stats Download patch file Download diff file Expand all files Collapse all files

2
src/backend/replication/walsender.c
View file

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

2
src/interfaces/libpq/fe-exec.c
View file

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