Commit2051fd3

Etsuro Fujita

committed

postgres_fdw: Fix comments in connection.c.

Commit27e1f14 missed updating some comments.Reviewed-by: Bharath RupireddyBackpatch-through: 14Discussion:https://postgr.es/m/CAPmGK15Q2Nm6U%2Ba_GwskrWFEVBZ9_3VKOvRrprGufpx91M_3Sw%40mail.gmail.com

1 parentef2e107 commit2051fd3Copy full SHA for 2051fd3

File tree

-6

lines changed

-6

lines changed

Lines changed: 4 additions & 6 deletions

Original file line number	Diff line number	Diff line change
`@@ -195,9 +195,9 @@ GetConnection(UserMapping user, bool will_prep_stmt, PgFdwConnState *state)`
`195`	`195`	`make_new_connection(entry,user);`
`196`	`196`
`197`	`197`	`/*`
`198`		`- * We check the health of the cached connection here whenstarting a new`
`199`		`- *remote transaction. If a broken connection is detected, we try to`
`200`		`- * reestablish a new connection later.`
	`198`	`+ * We check the health of the cached connection here whenusing it. In`
	`199`	`+ *cases where we're out of all transactions, if a broken connection is`
	`200`	`+ *detected, we try toreestablish a new connection later.`
`201`	`201`	`*/`
`202`	`202`	`PG_TRY();`
`203`	`203`	`{`
`@@ -213,9 +213,7 @@ GetConnection(UserMapping user, bool will_prep_stmt, PgFdwConnState *state)`
`213`	`213`	`ErrorData*errdata=CopyErrorData();`
`214`	`214`
`215`	`215`	`/*`
`216`		`- * If connection failure is reported when starting a new remote`
`217`		`- * transaction (not subtransaction), new connection will be`
`218`		`- * reestablished later.`
	`216`	`+ * Determine whether to try to reestablish the connection.`
`219`	`217`	`*`
`220`	`218`	`* After a broken connection is detected in libpq, any error other`
`221`	`219`	`* than connection failure (e.g., out-of-memory) can be thrown`

Comments

(0)