On Mon, May 6, 2024 at 04:15:24PM +0200, Laurenz Albe wrote:
> On Sun, 2024-05-05 at 20:25 +0000, PG Doc comments form wrote:
> > On this page:
> > https://www.postgresql.org/docs/14/server-start.html#CLIENT-CONNECTION-PROBLEMS
> >
> > It notes: ".... A common mistake is to forget to configure the server to
> > allow TCP/IP connections."
> >
> > I would expect a hyperlink to a section explaining exactly HOW to "configure
> > the server to allow TCP/IP connections" - from that note text.
>
> I agree.
>
> Perhaps it should say:
>
> A common mistake is to forget to configure "listen_addresses" so that the
> server accepts remote TCP connections.
>
> Then "listen_addresses" could hyperlink to the parameter's documentation.
Agreed, patch attached.
--
Bruce Momjian <br...@momjian.us> https://momjian.us
EDB https://enterprisedb.com
When a patient asks the doctor, "Am I going to die?", he means
"Am I going to die soon?"
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 2c4d5ef640d..933cac813c2 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -637,7 +637,8 @@ psql: error: connection to server at "server.joe.com" (123.123.123.123), port 54
This is the generic <quote>I couldn't find a server to talk
to</quote> failure. It looks like the above when TCP/IP
communication is attempted. A common mistake is to forget to
- configure the server to allow TCP/IP connections.
+ configure <xref linkend="guc-listen-addresses"/> so that the server
+ accepts remote TCP connections.
</para>
<para>
