From: Joe Conway Date: Sun, 8 Dec 2013 01:00:10 +0000 (-0800) Subject: Fix performance regression in dblink connection speed. X-Git-Tag: REL9_3_3~109 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0ec530625f1cc0a17d975f925fed5d3ab469c6f8;p=postgresql Fix performance regression in dblink connection speed. Previous commit e5de601267d98c5d60df6de8d436685c7105d149 modified dblink to ensure client encoding matched the server. However the added PQsetClientEncoding() call added significant overhead. Restore original performance in the common case where client encoding already matches server encoding by doing nothing in that case. Applies to all active branches. Issue reported and work sponsored by Zonar Systems. --- diff --git a/contrib/dblink/dblink.c b/contrib/dblink/dblink.c index e617f9b399..9fe750e993 100644 --- a/contrib/dblink/dblink.c +++ b/contrib/dblink/dblink.c @@ -209,7 +209,8 @@ typedef struct remoteConnHashEnt errdetail_internal("%s", msg))); \ } \ dblink_security_check(conn, rconn); \ - PQsetClientEncoding(conn, GetDatabaseEncodingName()); \ + if (PQclientEncoding(conn) != GetDatabaseEncoding()) \ + PQsetClientEncoding(conn, GetDatabaseEncodingName()); \ freeconn = true; \ } \ } while (0) @@ -288,8 +289,9 @@ dblink_connect(PG_FUNCTION_ARGS) /* check password actually used if not superuser */ dblink_security_check(conn, rconn); - /* attempt to set client encoding to match server encoding */ - PQsetClientEncoding(conn, GetDatabaseEncodingName()); + /* attempt to set client encoding to match server encoding, if needed */ + if (PQclientEncoding(conn) != GetDatabaseEncoding()) + PQsetClientEncoding(conn, GetDatabaseEncodingName()); if (connname) {