Hi. Per Coverity.
Coverity has some reports about pg_createsubcriber. CID 1591322: (#1 of 1): Resource leak (RESOURCE_LEAK) 10. leaked_storage: Variable dbname going out of scope leaks the storage it points to. Additionally there are several calls that are out of the ordinary, according to the Postgres API. According to the documentation: libpq-exec <https://www.postgresql.org/docs/current/libpq-exec.html> The correct function to free memory when using PQescapeLiteral and PQescapeIdentifier would be PQfreemem. Trivial fixes attached. best regards, Ranier Vilela
fix-resource-leak-and-api-misuse-pg_createsubcriber.patch
Description: Binary data
