From e75d99818dd3940be997520e64db8c9e3b207e39 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 21 May 2024 07:05:26 +0200 Subject: Merging upstream version 15.7. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/libpq-connect.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc/src/sgml/html/libpq-connect.html') diff --git a/doc/src/sgml/html/libpq-connect.html b/doc/src/sgml/html/libpq-connect.html index 0c6ebc1..01e4c59 100644 --- a/doc/src/sgml/html/libpq-connect.html +++ b/doc/src/sgml/html/libpq-connect.html @@ -1,5 +1,5 @@ -34.1. Database Connection Control Functions

34.1. Database Connection Control Functions

+34.1. Database Connection Control Functions

34.1. Database Connection Control Functions

The following functions deal with making a connection to a PostgreSQL backend server. An application program can have several backend connections open at @@ -518,7 +518,7 @@ PQsslKeyPassHook_OpenSSL_type PQgetSSLKeyPassHook_OpenSSL(void); connection parameters. There are two accepted formats for these strings: plain keyword/value strings and URIs. URIs generally follow - RFC + RFC 3986, except that multi-host connection strings are allowed as further described below.

34.1.1.1. Keyword/Value Connection Strings

@@ -582,7 +582,7 @@ postgresql:///mydb?host=localhost&port=5433 of ssl=true are translated into sslmode=require.

- The connection URI needs to be encoded with percent-encoding + The connection URI needs to be encoded with percent-encoding if it includes symbols with special meaning in any of its parts. Here is an example where the equal sign (=) is replaced with %3D and the space character with @@ -1131,4 +1131,4 @@ postgresql://%2Fvar%2Flib%2Fpostgresql/dbname mode

-

\ No newline at end of file +

\ No newline at end of file -- cgit v1.2.3