From cacbdd78106526d7c4f11f90b538f96ba8696fb0 Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Thu, 31 Oct 2013 10:55:59 -0400 Subject: Use appendStringInfoString instead of appendStringInfo where possible. This shaves a few cycles, and generally seems like good programming practice. David Rowley --- contrib/postgres_fdw/postgres_fdw.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'contrib/postgres_fdw/postgres_fdw.c') diff --git a/contrib/postgres_fdw/postgres_fdw.c b/contrib/postgres_fdw/postgres_fdw.c index 8713eabc646..246a3a985b7 100644 --- a/contrib/postgres_fdw/postgres_fdw.c +++ b/contrib/postgres_fdw/postgres_fdw.c @@ -787,7 +787,7 @@ postgresGetForeignPlan(PlannerInfo *root, root->parse->commandType == CMD_DELETE)) { /* Relation is UPDATE/DELETE target, so use FOR UPDATE */ - appendStringInfo(&sql, " FOR UPDATE"); + appendStringInfoString(&sql, " FOR UPDATE"); } else { @@ -808,11 +808,11 @@ postgresGetForeignPlan(PlannerInfo *root, { case LCS_FORKEYSHARE: case LCS_FORSHARE: - appendStringInfo(&sql, " FOR SHARE"); + appendStringInfoString(&sql, " FOR SHARE"); break; case LCS_FORNOKEYUPDATE: case LCS_FORUPDATE: - appendStringInfo(&sql, " FOR UPDATE"); + appendStringInfoString(&sql, " FOR UPDATE"); break; } } -- cgit v1.2.3