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 1qABrJ-0004QP-1R for pgsql-general@arkaria.postgresql.org; Fri, 16 Jun 2023 15:59:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qABrH-0000i5-Tj for pgsql-general@arkaria.postgresql.org; Fri, 16 Jun 2023 15:59:31 +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 1qABrH-0000g9-J2 for pgsql-general@lists.postgresql.org; Fri, 16 Jun 2023 15:59:31 +0000 Received: from mail-yw1-x112d.google.com ([2607:f8b0:4864:20::112d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qABrB-002YR0-LP for pgsql-general@lists.postgresql.org; Fri, 16 Jun 2023 15:59:27 +0000 Received: by mail-yw1-x112d.google.com with SMTP id 00721157ae682-56d378b75f0so10359727b3.1 for ; Fri, 16 Jun 2023 08:59:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686931165; x=1689523165; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=WgSKCLrsEc+BWMYp/j1fMag//+4jtADU4xOQJ49sdKo=; b=dbJIAljR5y0rr1SiZtmm111NxZtUU85q7XHpmH7ah+TpPa7glzOzEyrKUzK+nP2jUr 821GzZ5k3R7YeFOdQXyK62kltmphftCFZNtsCzgYu7y0NP5/J+ML2jck5IFYRiX/FWqS w81J/npLfja9KQxJ1Gd0FvZ2xmtXoknFeODX+4Cf4BBatvhrzZ6tfOqBTiD9Cw3PDf/K FIxBpIn8fwaSP+YyVPG4HkQnb9RXTm39FjDi2tt8/MTHu/rwk8W2kU1u2kPtnDeRVI0F ErGaWn1Niii8+Js8LU7l9t2AVee3tK/8gpQvKnCCwIpThmZWlQRWRuUQ14rw4KfDMu5g BB0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686931165; x=1689523165; 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:subject:date:message-id:reply-to; bh=WgSKCLrsEc+BWMYp/j1fMag//+4jtADU4xOQJ49sdKo=; b=RrFaE5oY6WaVUNCMQNGW6fTXd+ICbhgr0QfuFDTzT1WnTWm7dmKGVc3gfOD8cG7+fU 7Hx/EQRdyKSy9eO/s6ZvPc9RfvI9k1B48YT4Jfc0mrdZA0WX6jqT7hSFbCAQ2vFH9u0P IEQL+CpTPL4r/FlnoiYG2fjR0fNZgQLm23sdnl/3KDJ6dzyCkPbxjvx4DAu+0Tagpgfd 7lDzTULk0fldAmWNRtpqQ1x5S438/k1lSIBXBr93v5M9i8H7GUDjw8s9uYSlbvcmIE9e TkHDbFtm2m6sqgq7x04jBW7jN9fruhvYaXj4HotZ9WvLb7aXv7qhglmJHrmalXk3uBEQ sWJw== X-Gm-Message-State: AC+VfDwEqAhbr/X9gEWBZF38wMEIsvjWVgFFL35Z04s2BKQUaioYPG3O wuc0PP6oGmTpg7oqrZqe2ct6rZM+lqI= X-Google-Smtp-Source: ACHHUZ76Ehrzu9Vbw7jBN0wQu1FXS0jtbuaFJUccBpSlnnJdD8uVIzFPT7lLNETzGNiWve8uckMVbQ== X-Received: by 2002:a81:7dd7:0:b0:56d:c97:39f4 with SMTP id y206-20020a817dd7000000b0056d0c9739f4mr1988649ywc.8.1686931164741; Fri, 16 Jun 2023 08:59:24 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:f889:4059:a055:b96e? ([2600:1700:bd2c:b810:f889:4059:a055:b96e]) by smtp.googlemail.com with ESMTPSA id l126-20020a819484000000b0056cff012ee3sm4013509ywg.121.2023.06.16.08.59.24 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 16 Jun 2023 08:59:24 -0700 (PDT) Message-ID: <868e1ff2-1625-c362-b373-9f4627ea9b65@gmail.com> Date: Fri, 16 Jun 2023 10:59:24 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Question: Multiple pg clusters on one server can be reached with the standard port. Content-Language: en-US To: pgsql-general@lists.postgresql.org References: <4d70ad6a5a73b9e9faaf8f2715cac862c86def3c.camel@cybertec.at> <6ba275cd2d442a913a234564aeaec27311ec1d16.camel@cybertec.at> <71943c04e05c3c13d5cd2b287909f351@weiller.eu> <6e8947e1d4394082e27f1f8354ae5d4f@weiller.eu> <507b783267640f0b8dd6b6fdc0f132fa27cb4212.camel@cybertec.at> <1162c17ba0aec0c5ee9a7052c49036ec@weiller.eu> From: Ron In-Reply-To: <1162c17ba0aec0c5ee9a7052c49036ec@weiller.eu> 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 6/16/23 10:54, Brainmue wrote: > 16. Juni 2023 17:41, "Ron" schrieb: > >> On 6/16/23 10:18, Laurenz Albe wrote: >> >>> On Fri, 2023-06-16 at 14:49 +0000, Brainmue wrote: >> 16. Juni 2023 14:50, "Laurenz Albe" schrieb: >>> On Fri, 2023-06-16 at 12:35 +0000, Brainmue wrote: >>> >>> We want to minimise dependencies between the application and the associated PostgreSQL DB. >>> The idea is that the application gets its DB alias and this is then used as a connection string. >>> This way we can decide in the backend on which server the PostgreSQL DB is running. >>> There is an existing solution for that: the libpq connection service file: >>> https://www.postgresql.org/docs/current/libpq-pgservice.html >>> >>> If you want to manage the connection strings centrally, you can use LDAP lookup: >>> https://www.postgresql.org/docs/current/libpq-ldap.html >> Thank you, I already know this solution, but the LDAP solution is out of the question for us and >> the file again means an intervention on the client. And that's exactly what we don't want. >>> Okay. >>> >>> Then why don't you go with your original solution, but use a unique TCP port number >>> for each database? There are enough port numbers available. That way, there is no >>> collision and no need for a proxy to map port numbers. >> In practice, that gets very complicated is large organizations: every time you add another >> database, you must file another request with the CISO RISK office to get yet another non-standard >> port open from dozens of machines, and the network team implement them. >> >> Operationally much simpler to have a listener handle that. >> >> -- Born in Arizona, moved to Babylonia. > Hello Ron, > > I have to agree with you there as well. The workflow you have to go through is also often a time > issue. > There are many places that have to agree and then application owners still have to provide > justifications. > At the same time, we have to be flexible and fast and allocate the resources well at any time and > provide the application with the maximum possible performance. There's always The Cloud...  spinning up a new AWS RDS Postgresql is fast and simple.  (Costly, though.) -- Born in Arizona, moved to Babylonia.