Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oM8wa-0000Ka-BC for pgsql-admin@arkaria.postgresql.org; Thu, 11 Aug 2022 14:13:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oM8wZ-0002TN-7B for pgsql-admin@arkaria.postgresql.org; Thu, 11 Aug 2022 14:13:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oM8wY-0002TD-SX for pgsql-admin@lists.postgresql.org; Thu, 11 Aug 2022 14:13:50 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oM8wW-0004sJ-Mo for pgsql-admin@postgresql.org; Thu, 11 Aug 2022 14:13:49 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 27BEDMpA484837; Thu, 11 Aug 2022 10:13:22 -0400 From: Tom Lane To: richard coleman cc: "David G. Johnston" , Scott Ribe , pgsql-admin Subject: Re: postgresql definitive list of network resources used/needed? In-reply-to: References: <200DE464-2992-4D0C-96F1-6656E1CE932A@elevated-dev.com> <384610.1660168232@sss.pgh.pa.us> Comments: In-reply-to richard coleman message dated "Thu, 11 Aug 2022 09:17:50 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <484835.1660227202.1@sss.pgh.pa.us> Date: Thu, 11 Aug 2022 10:13:22 -0400 Message-ID: <484836.1660227202@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk richard coleman writes: > Is it correct to state that (barring the soon to be obsolete stats > collector): > - PostgreSQL only uses the configured port, who's default is 5432, via > tcp > - outgoing connections are all tcp and use random ports There are no outgoing connections in basic PG, unless maybe you enable log_hostname, and then it'd depend on what your libc does for DNS lookup --- but that'd more likely be UDP than TCP. > - none of the other intrinsic features; replication, pg_dump, > pg_basebackup, pg_restore, etc. use any other network ports Replication surely requires some sort of connection, although it could be either outgoing or incoming depending on your setup. I'm also getting rather confused by what you mean by "use a port", if you think that clients such as pg_dump don't. > - network ports used by extensions, even if included in the base > install, are beyond the scope of PostgreSQL documentation If we were to start adding this sort of info to the docs, it'd be appropriate to document the behavior of each included extension in the documentation file for that extension. As I go through these examples, though, I grow less enthusiastic about it being a useful exercise at all. regards, tom lane