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 1oLtDt-0001gP-AE for pgsql-admin@arkaria.postgresql.org; Wed, 10 Aug 2022 21:26:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oLtDs-0004CC-60 for pgsql-admin@arkaria.postgresql.org; Wed, 10 Aug 2022 21:26:40 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oLtDr-0004C2-PH for pgsql-admin@lists.postgresql.org; Wed, 10 Aug 2022 21:26:39 +0000 Received: from mail-ot1-x332.google.com ([2607:f8b0:4864:20::332]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oLtDp-0003CU-Nr for pgsql-admin@lists.postgresql.org; Wed, 10 Aug 2022 21:26:39 +0000 Received: by mail-ot1-x332.google.com with SMTP id r10-20020a056830448a00b0063711786b01so3637435otv.11 for ; Wed, 10 Aug 2022 14:26:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=Z3CV3PoQpunQL1IGEirEEgEbcaM1eL2OuhfKOEXGOnI=; b=NHwc8QCdw9o9XJVrBMKXWkEZMkqwgPBabdgzPX7tiJtzuON3zTs87bCKtcvbvYk8+D 9r5ii6OapdaYtatsoFaq3SgR+9YkQeZ09ZRrjF7KWispRj38frMr4uXdULm2ShZthwoA HgKxd4+fDY35HbOfHBxiEHUH353TnHOXn8x/taCUs7XBzhxwVqdVGcUHU9f9SC5CilW6 N38tMuZHxIWzL8+OfmwcJNWzsmIVUwc0ontD2D0Z9JI2nZX8Zyl2XhkkoyC7kZvsXy6s cO1uepZWF5nTBBJu3H3aUw3E0i2k1crzQAXB3D0ayHq8AmX+QPWIq5ef+oGbhDVZrD9b Ba8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=Z3CV3PoQpunQL1IGEirEEgEbcaM1eL2OuhfKOEXGOnI=; b=okyNQLgSdKiQLxwNVs7janj/i9/EUSRio2+0pbZsodhaDoumhN0cfq+XaPNHFTh7KO L1rs+5tr7Wh3IGCjvfxiqC3se0HiCdPTYnocuJawuwTU4JmxwtCkqeJ5Bw089sramEsF kzrt4tdDgp2BTr19Zuh19DnTjMsfrwxrtACAQdP2MmgeANf4c4+VL5KGoO2GO8hR1Vhi Bhl3VF5LEZuvHuv+5qETHONOyyrwrs3CSdJPNIQJ4UnniisIlDpSyLsRVHboMPMtN+3y y4G5eg8NKxKeRFzFtzGY+9qRUJU2oV5EyXAp4FQBuesUEvLS8xI2HzHGCp7QQMAfNoOA x6Rg== X-Gm-Message-State: ACgBeo3h4XOYRzrW/823gdro5gnnh5XaYqkkg9/4f6sm0ccD8rAiGj4A YNTfKenO/yzn/MpVB4rrSaeKODTSZjk= X-Google-Smtp-Source: AA6agR7CvawHRu3Mpd3qKOsTRDXacIxsabaQGZmhKbZ/xb2Yu02sMBWNGjEUvCDmCXS1X+dufKLwVA== X-Received: by 2002:a05:6830:44a3:b0:637:c53:5f55 with SMTP id r35-20020a05683044a300b006370c535f55mr3428143otv.256.1660166795138; Wed, 10 Aug 2022 14:26:35 -0700 (PDT) Received: from [192.168.88.10] (ip68-11-68-85.no.no.cox.net. [68.11.68.85]) by smtp.googlemail.com with ESMTPSA id o15-20020a4aabcf000000b0044103bb6e23sm818655oon.25.2022.08.10.14.26.34 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 10 Aug 2022 14:26:34 -0700 (PDT) Message-ID: <173f35ba-61e7-fef3-b567-38455aecd5b0@gmail.com> Date: Wed, 10 Aug 2022 16:26:34 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: postgresql definitive list of network resources used/needed? Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: From: Ron In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 8/10/22 16:08, richard coleman wrote: > I'm currently standing up a number of PostgreSQL 14 servers.  There is a > question concerning ports and protocols required or used by PostgreSQL.  > Unfortunately, I can't seem to find any such listing.  Most references > only mention the primary connection port, ex: tcp 5432. > > Apparently, I've discovered that PostgreSQL connects to itself over UDP.  > I've also discovered, while looking at the network while one of our server > was running PostgreSQL, that while there were a number of connections > between local 5432 and a random remote port, That's how TCP IP works; you see the same with ssh, http, dns, etc, etc. > there was also a connection from a local random port to a remote 5432. A local process connecting to a remote postgresql database. >   If these ports were closed and only 5432 left open, this connection > would have failed. > > Does anyone know where I might find the definitive listing of ports and > protocols used by PostgreSQL? I'm pretty sure I only ever requuest that TCP 5432 be opened in the firewall, and that as incoming to the DB server. -- Angular momentum makes the world go 'round.