pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: k.man.113@gmail.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Connection Info
Date: Wed, 16 Oct 2024 21:36:00 -0400
Message-ID: <ZxBqAJ37NmchyvVI@momjian.us> (raw)
In-Reply-To: <f87054fdc3ba5f4fd3ef986c413b0d5cbe21e6f4.camel@cybertec.at>
References: <171494070007.703.17021965362263796980@wrigleys.postgresql.org>
	<f87054fdc3ba5f4fd3ef986c413b0d5cbe21e6f4.camel@cybertec.at>

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  <bruce@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?"

Attachments:

  [text/x-diff] listen.diff (659B, ../ZxBqAJ37NmchyvVI@momjian.us/2-listen.diff)
  download | inline diff:
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>

view thread (5+ messages)  latest in thread

Message-ID: <ZxBqAJ37NmchyvVI@momjian.us>
Permalink:  ../ZxBqAJ37NmchyvVI@momjian.us/
Also on:    postgresql.org/message-id/ZxBqAJ37NmchyvVI@momjian.us

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: bruce@momjian.us, laurenz.albe@cybertec.at, k.man.113@gmail.com, pgsql-docs@lists.postgresql.org
  Subject: Re: Connection Info
  In-Reply-To: <ZxBqAJ37NmchyvVI@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox