postgres.git / summary / log / commit / refs

commit    fa78e5bea53a3096d1df7d1b2d7cbd58d15a9b7a
Author:   Peter Eisentraut <peter@eisentraut.org>
Date:     Thu Oct 30 09:59:56 2025 +0000
First released in: 18.1

    docs: Link to the correct protocol version inspection function
    
    The docs for max_protocol_version suggested PQprotocolVersion()
    instead of PQfullProtocolVersion() to find out the exact protocol
    version.  Since PQprotocolVersion() only returns the major protocol
    version, that is bad advice.
    
    Author: Jelte Fennema-Nio <postgres@jeltef.nl>
    Reviewed-by: Shinya Kato <shinya11.kato@gmail.com>
    Discussion: https://www.postgresql.org/message-id/flat/CAGECzQSKFxQsYAgr11PhdOr-RtPZEdAXZnHx6U3avLuk3xQaTQ%40mail.gmail.com


 doc/src/sgml/libpq.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index b2c2cf9eac8..cbb29b6ed40 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -2220,7 +2220,7 @@ postgresql://%2Fvar%2Flib%2Fpostgresql/dbname
         server does not support the protocol version requested by the client,
         the connection is automatically downgraded to a lower minor protocol
         version that the server supports. After the connection attempt has
-        completed you can use <xref linkend="libpq-PQprotocolVersion"/> to
+        completed you can use <xref linkend="libpq-PQfullProtocolVersion"/> to
         find out which exact protocol version was negotiated.
        </para>
 


[parent: bf3dba508ee1]