Skip to content

Commit ab66645

Browse files
committed
Doc: remove misleading claim in documentation of PQreset().
This text claimed that the reconnection would occur "to the same server", but there is no such guarantee in the code, nor would insisting on that be an improvement. Back-patch to v10 where multi-host connection strings were added. Discussion: https://postgr.es/m/1095901.1611268376@sss.pgh.pa.us
1 parent 0a9ae44 commit ab66645

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/src/sgml/libpq.sgml

+3-3
Original file line numberDiff line numberDiff line change
@@ -645,8 +645,8 @@ void PQreset(PGconn *conn);
645645

646646
<para>
647647
This function will close the connection
648-
to the server and attempt to reestablish a new
649-
connection to the same server, using all the same
648+
to the server and attempt to establish a new
649+
connection, using all the same
650650
parameters previously used. This might be useful for
651651
error recovery if a working connection is lost.
652652
</para>
@@ -669,7 +669,7 @@ PostgresPollingStatusType PQresetPoll(PGconn *conn);
669669

670670
<para>
671671
These functions will close the connection to the server and attempt to
672-
reestablish a new connection to the same server, using all the same
672+
establish a new connection, using all the same
673673
parameters previously used. This can be useful for error recovery if a
674674
working connection is lost. They differ from <xref linkend="libpq-PQreset"/> (above) in that they
675675
act in a nonblocking manner. These functions suffer from the same

0 commit comments

Comments
 (0)