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 1pzjZa-0005Do-GK for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 19:46:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzjZZ-0002BG-7X for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 19:46:01 +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 1pzjZY-0002B7-Sm for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 19:46:00 +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 1pzjZW-000Xlk-6Q for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 19:45:59 +0000 Received: by mail-yw1-x112d.google.com with SMTP id 00721157ae682-56190515833so972737b3.0 for ; Thu, 18 May 2023 12:45:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684439157; x=1687031157; h=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=ahWm3M/8vZVP7ihFEneN9vRZt/TE82teoaSRQmsiwA4=; b=pR+QzEeHtmumBFfFnSAwoHF4oiYLqp73MiMEoqiHnZGhppIy2iOQ72jGwieNUBRCnl nmOpn9s4hbx6F5my5cYclXC9wUTKWQSwKCZX+LyJ6OVY++A5NolAwGVJYHgebYk8/ys0 yiuxrzbdixTsSOmpgi2NNl4IvwWoIvsacsrs7/T1+H424Jk7niEHKzFdt8PNhX93SDaW FYDJkMUtDd+SfLUWca74IV6sYAGTRgvjM6G5+HFVdDtuyrIDHO7W8Uqk5d8dydiW7nhb xAFWNBpCfFwQJS4pNie808g/EiuNEdKeZ8gHGfJ0s1OfLqhhISCaFWrd88WtQMa6eFiW uynw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684439157; x=1687031157; h=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=ahWm3M/8vZVP7ihFEneN9vRZt/TE82teoaSRQmsiwA4=; b=ljuCkIhRKPG+j4KWv3PgyRdNtYM9FV9hHmqXhPDtK56z85s1V5Z4FtnahUtGnf1WXD 2NM/FrQsS21q7cOP/CwqYbLO//VD9Cvdxa3pJJh1AT17X3IZQcJIlx0ruGftcW4N6/8S +2nl0ja83rTSDn+LDZL5RnkrKsCYnJ0JZUwOS4+BGY0MSQU20iNlMa5dxF4KMD6hHQaw 5MQj3/1IQskD5OlgkH+vzHGDAJzV/u5/52askvyHkabboHk6rWQ7j9kthkzOkThY7usz k9MZqkN/y9n06oAEykvq0Kf+mWAGKHqCbrWmyp/JAXuS2XdN3RBjYumpzVcQxK4Q85Ke c+rA== X-Gm-Message-State: AC+VfDx1ydllIJLOXsTX/DiPSzR6KlkbeDZdoB8/jNAok7h0HdUTy89Y Sos+L9M1LsqUJFGsT45OtSOVCmI4MSk= X-Google-Smtp-Source: ACHHUZ65b30bcJ9iEbms2y9XCkmijCKqB4wgZEdVkNERV/wrhGitrJPJMXz8ICEDdqhgb8b+DidXSQ== X-Received: by 2002:a0d:d9ce:0:b0:55a:3502:d2ca with SMTP id b197-20020a0dd9ce000000b0055a3502d2camr129939ywe.13.1684439157048; Thu, 18 May 2023 12:45:57 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:1894:39f8:bd0e:1dc4? ([2600:1700:bd2c:b810:1894:39f8:bd0e:1dc4]) by smtp.googlemail.com with ESMTPSA id g131-20020a0ddd89000000b00545b02d4af5sm642828ywe.48.2023.05.18.12.45.56 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 May 2023 12:45:56 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------xKzVoOK4I70WLpu0HOZeNm68" Message-ID: Date: Thu, 18 May 2023 14:45:56 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? Content-Language: en-US To: pgsql-general@lists.postgresql.org References: <7636ea3e-fab7-1681-4e7e-464faa2d127f@gmail.com> From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------xKzVoOK4I70WLpu0HOZeNm68 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 5/18/23 14:07, Thorsten Glaser wrote: > On Thu, 18 May 2023, Ron wrote: > >>> Why not using multiple clusters then? >> Yet More Firewall Rules to get approved by the Security Team.  And then they >> balk at port 5433 because they've never heard of it. > But mixing multiple customers on one cluster is much more of a risk. Better have your roles and pg_hba.conf entries defined correctly! Fortunately, pg_hba.conf is pretty easy. >> And from a technical point of view, one Postgresql system can better manage the >> memory on a VM than two which don't know about each other. > Probably true. Is there something with which multiple clusters running > on the same server can communicate to do that better? A /meta/ postmaster!!! -- Born in Arizona, moved to Babylonia. --------------xKzVoOK4I70WLpu0HOZeNm68 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 5/18/23 14:07, Thorsten Glaser wrote:
On Thu, 18 May 2023, Ron wrote:

Why not using multiple clusters then?
Yet More Firewall Rules to get approved by the Security Team.  And then they
balk at port 5433 because they've never heard of it.
But mixing multiple customers on one cluster is much more of a risk.

Better have your roles and pg_hba.conf entries defined correctly!

Fortunately, pg_hba.conf is pretty easy.

And from a technical point of view, one Postgresql system can better manage the
memory on a VM than two which don't know about each other.
Probably true. Is there something with which multiple clusters running
on the same server can communicate to do that better?

A meta postmaster!!!

--
Born in Arizona, moved to Babylonia.
--------------xKzVoOK4I70WLpu0HOZeNm68--