From 1b4d52c3556b9abad10165ce7298062cf7eb7005 Mon Sep 17 00:00:00 2001 From: Daniel Gustafsson Date: Tue, 1 Oct 2024 10:20:14 +0200 Subject: [PATCH] doc: Mention the connstring key word for PGSERVICE MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit The documentation for the connection service file was mentioning the environment variable early but not the connection string key word until the last sentence and only then in an example. This adds the keyword in the first paragraph to make it clearer Author: Dagfinn Ilmari Mannsåker Discussion: https://postgr.es/m/87r09ibpke.fsf@wibble.ilmari.org --- doc/src/sgml/libpq.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 4a727d4499..e56c12acfa 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -9318,7 +9318,8 @@ myEventProc(PGEventId evtId, void *evtInfo, void *passThrough) The connection service file allows libpq connection parameters to be associated with a single service name. That service name can then be - specified in a libpq connection string, and the associated settings will be + specified using the service key word + in a libpq connection string, and the associated settings will be used. This allows connection parameters to be modified without requiring a recompile of the libpq-using application. The service name can also be specified using the PGSERVICE environment variable. -- 2.39.5