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 1pQ93x-0006a8-Qc for pgsql-general@arkaria.postgresql.org; Thu, 09 Feb 2023 15:42:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pQ93w-0005cs-Nb for pgsql-general@arkaria.postgresql.org; Thu, 09 Feb 2023 15:42:16 +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 1pQ93w-0005ce-Cq for pgsql-general@lists.postgresql.org; Thu, 09 Feb 2023 15:42:16 +0000 Received: from mail-ed1-x52e.google.com ([2a00:1450:4864:20::52e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pQ93u-0003YN-5B for pgsql-general@postgresql.org; Thu, 09 Feb 2023 15:42:15 +0000 Received: by mail-ed1-x52e.google.com with SMTP id da9so2401457edb.12 for ; Thu, 09 Feb 2023 07:42:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=Cjt6QT9fpgXOx5numXJtdDzPr9krL656Z6MNHYocNZ8=; b=P39JMLGP97rFsqm8RDN0DFDucEcPhqsk0E3DLMZuxXY1rLQjXMpQYmHjuhoiu7BtQI LINsGEad1w3YSLlwnRkrilvM/ONtZUos8IMS6/i8KfWGWRT7Rcr5sSpOCx6xbo9Gb8ZG ZO39imOJcxGwJpZYIdiBCkrHHO3Quq+xZ+j8lJHet6YV8DYkwmAwG0W41DJpylYsgaMa Bp5V2h6dd/K+JdzLVD7Cy/B2+PinlLLp9PWXo3EdFXbQNtUxdBNcLcNr+9UF5dshoEre XUedhk1EdD329ys4QMZsajmglkwSpbQqwNyjnwA+OhVbvR8guQ6GpjeN/bZ5zQd5pPNu F2RA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Cjt6QT9fpgXOx5numXJtdDzPr9krL656Z6MNHYocNZ8=; b=Sxyt2RBxzDjVe0bLk1WYvveYPGWbPUXSWdz6O6d74AwnArK1irguReAsYmFp/c6JCN 0gF39M0Ol6WTqg9H55CrBr1gwpqV776TzC5W5LxnqFemiN9AuMM6yoMhGsxFDdj0q8NX QddltL9x31Ai2Cxq5OKbNA852RXVNH+ThP3i/fsuf7xDcXYX1WwdA9ukrGm5TU1sXDuo RBgGHcA1YxLmuqJeBn59XcC7qvlUiEcRQ7Lv55qAqEy6LotdWCmi6p1hvp48XL96BoR5 makMmWfLb++Wk1t143sHwFnB29gM7CTLi3K4P3ayW42cPBxOdXwwnyBxSSXJd153IrhX elPA== X-Gm-Message-State: AO0yUKVw4N8cs3dF9MeShij3bb33MMSuEDuSxM2Bo00AgXov0ErGrKxZ wOLvEQ1PuoOwMFl3NRBKIykr9g== X-Google-Smtp-Source: AK7set+Aggb4mgyEFnpKs5TzzbGms81Sf09B1wIcOFOpo8idi2vLj325gcSTAJC6kR5Hi3BKx5US/g== X-Received: by 2002:a05:6402:4507:b0:4a3:43c1:8431 with SMTP id ez7-20020a056402450700b004a343c18431mr8426489edb.5.1675957332815; Thu, 09 Feb 2023 07:42:12 -0800 (PST) Received: from localhost.localdomain (ip5f5aedce.dynamic.kabel-deutschland.de. [95.90.237.206]) by smtp.gmail.com with ESMTPSA id ci4-20020a170906c34400b0087873afb1b4sm1017804ejb.41.2023.02.09.07.42.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 09 Feb 2023 07:42:12 -0800 (PST) Message-ID: <2eef5146f9836742de02d9db5cbe6cc8a4e3827d.camel@cybertec.at> Subject: Re: PostgreSQL From: Laurenz Albe To: Joseph Kennedy , Stephen Frost Cc: Giovanni Biscontini , pgsql-general@postgresql.org Date: Thu, 09 Feb 2023 16:42:05 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.3 (3.46.3-1.fc37) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 2023-02-09 at 09:54 +0100, Joseph Kennedy wrote: > As I wtote,=C2=A0I would like restrict access to sensitive or restricted = information > for some users (eg. hide data of one or more clients for some database us= ers). >=20 > My question is: do you know some other solution to do that ?=C2=A0 It is easy to hide data from users: use permissions or row level security. It is impossible to hide metadata from users, but we don't consider that a = problem. If you want that, use a database or a database cluster per user. Yours, Laurenz Albe