mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

postgres_fdw: Fix comments in connection.c.

Browse Source 
Commit 27e1f1456 missed updating some comments.

Reviewed-by: Bharath Rupireddy
Backpatch-through: 14
Discussion: https://postgr.es/m/CAPmGK15Q2Nm6U%2Ba_GwskrWFEVBZ9_3VKOvRrprGufpx91M_3Sw%40mail.gmail.com
This commit is contained in:
Etsuro Fujita 2021-10-07 18:15:01 +09:00
parent ef2e107f54
commit 2051fd30a4
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
contrib/postgres_fdw/connection.c
View File

@ -195,9 +195,9 @@ GetConnection(UserMapping *user, bool will_prep_stmt, PgFdwConnState **state)
make_new_connection(entry, user); make_new_connection(entry, user);
/* /*
* We check the health of the cached connection here when starting a new * We check the health of the cached connection here when using it. In
* remote transaction. If a broken connection is detected, we try to * cases where we're out of all transactions, if a broken connection is
* reestablish a new connection later. * detected, we try to reestablish a new connection later.
*/ */
PG_TRY(); PG_TRY();
{ {
@ -213,9 +213,7 @@ GetConnection(UserMapping *user, bool will_prep_stmt, PgFdwConnState **state)
ErrorData *errdata = CopyErrorData(); ErrorData *errdata = CopyErrorData();
/* /*
* If connection failure is reported when starting a new remote * Determine whether to try to reestablish the connection.
* transaction (not subtransaction), new connection will be
* reestablished later.
* *
* After a broken connection is detected in libpq, any error other * After a broken connection is detected in libpq, any error other
* than connection failure (e.g., out-of-memory) can be thrown * than connection failure (e.g., out-of-memory) can be thrown