diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2017-09-13 08:31:03 -0400 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2017-09-13 08:32:09 -0400 |
| commit | 2b0ded5060cc2e0b7d6c765af5b5f7334f64f5dc (patch) | |
| tree | cc9bfaab5ed2e66c7c69835f5adf3e292fd2cae6 | |
| parent | b1705f35f805933629520eded68b82d2a2900871 (diff) | |
| download | postgresql-2b0ded5060cc2e0b7d6c765af5b5f7334f64f5dc.tar.gz postgresql-2b0ded5060cc2e0b7d6c765af5b5f7334f64f5dc.zip | |
Improve error message in WAL sender
The previous error message when attempting to run a general SQL command
in a physical replication WAL sender was a bit sloppy.
Reported-by: Fujii Masao <masao.fujii@gmail.com>
| -rw-r--r-- | src/backend/replication/walsender.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/replication/walsender.c b/src/backend/replication/walsender.c index db346e6edbd..1fbe8ed71b0 100644 --- a/src/backend/replication/walsender.c +++ b/src/backend/replication/walsender.c @@ -1545,7 +1545,7 @@ exec_replication_command(const char *cmd_string) case T_SQLCmd: if (MyDatabaseId == InvalidOid) ereport(ERROR, - (errmsg("not connected to database"))); + (errmsg("cannot execute SQL commands in WAL sender for physical replication"))); /* Tell the caller that this wasn't a WalSender command. */ return false; |