diff options
| author | Fujii Masao <fujii@postgresql.org> | 2021-12-03 17:35:29 +0900 |
|---|---|---|
| committer | Fujii Masao <fujii@postgresql.org> | 2021-12-03 17:37:19 +0900 |
| commit | 21a86b0eba64df8188463a0e497dd323e6909e31 (patch) | |
| tree | 214bd86302ccda45e900221dfc1d267d18f00528 /src/backend/access/transam/commit_ts.c | |
| parent | 3e644dcca1e97d7f4276dc2233c467addb179c88 (diff) | |
| download | postgresql-21a86b0eba64df8188463a0e497dd323e6909e31.tar.gz postgresql-21a86b0eba64df8188463a0e497dd323e6909e31.zip | |
postgres_fdw: Fix unexpected reporting of empty message.
pgfdw_report_error() in postgres_fdw gets a message from PGresult or
PGconn to report an error received from a remote server. Previously
if it could get a message from neither of them, it reported empty
message unexpectedly. The cause of this issue was that pgfdw_report_error()
didn't handle properly the case where no message could be obtained
and its local variable message_primary was set to '\0'.
This commit improves pgfdw_report_error() so that it reports the message
"could not obtain ..." when it gets no message and message_primary
is set to '\0'. This is the same behavior as when message_primary is NULL.
dblink_res_error() in dblink has the same issue, so this commit also
improves it in the same way.
Back-patch to all supported branches.
Author: Fujii Masao
Reviewed-by: Bharath Rupireddy
Discussion: https://postgr.es/m/477c16c8-7ea4-20fc-38d5-ed3a77ed616c@oss.nttdata.com
Diffstat (limited to 'src/backend/access/transam/commit_ts.c')
0 files changed, 0 insertions, 0 deletions