Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tBOmk-003aBg-Mi for pgsql-general@arkaria.postgresql.org; Thu, 14 Nov 2024 01:36:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tBOmi-0009Pp-1Y for pgsql-general@arkaria.postgresql.org; Thu, 14 Nov 2024 01:36:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tBOmh-0009Pg-Md for pgsql-general@lists.postgresql.org; Thu, 14 Nov 2024 01:36:36 +0000 Received: from mail-oi1-x235.google.com ([2607:f8b0:4864:20::235]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tBOmb-001o9l-51 for pgsql-general@lists.postgresql.org; Thu, 14 Nov 2024 01:36:35 +0000 Received: by mail-oi1-x235.google.com with SMTP id 5614622812f47-3e6048bc23cso34478b6e.3 for ; Wed, 13 Nov 2024 17:36:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731548188; x=1732152988; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Xf6LZpicQfU7ymKJ32bQo+zJ9WwTJF7GOFEofRw59R8=; b=T/Gs+3XlmKJdHOmtHnKRPlWa6LwEVdgCtnYALvDmPCHzZ3wwXhFS3hP58rXg/p/u/v cXYHv8l5p6BrlwN6QyNV4SOuARmLf7L8dQiJ5MO+wTSadFDd753hbi3lfapYxizrigz7 G9KrPDJl7BkqzFt3qwcbPCW2EVAYMu2rSkKf97t7RRT8eR/tf/EyE1a3RcX2GsqYB1KR B8D2M87z+MI9br1ukMWkHGvBPvi2iIJJ93MdSijbEmjbj8qPYQfrXRxpmR7C1gIaGeYk jRPVbnOeYVHpA7A8vwTgUh9kYRzuHtZ36VT7t+V+gDeQGQnjGXJgIgdlnIaeDEGf+TiT SJYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731548188; x=1732152988; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Xf6LZpicQfU7ymKJ32bQo+zJ9WwTJF7GOFEofRw59R8=; b=OSnN0Guzlo0UN0hgVbvQH1OcdnqkYRVu3SOHgIMHi8zlkj7YUevqnebEQU/1ofqVIy 4IWB9NZRxAaJ3HmKviG+pYNzQ89k5Xh3F9Ewtpha0FkwdoDepqpjn0hnLGuE5B1wPgMY Hz37MJfQ789jXQDt4eObVOcn3Yv0fTYcBIKyGNSs0jEtrxrqeJWvngj+FnL4hH5n23KA 9g5lgBLg8MGpUN65rOoHDvh+9g97eYLeW/kQAEzOb0qaV4qmb536w6ldR+4o9/HoRZPv F0Q/nuKAnsfF4Qt6da3re6JhoZcXr23bTVptg6bFsIaC4omzViMCEI7cYnyc0qVfT5vU 73XQ== X-Gm-Message-State: AOJu0YxFohqr11muNXRExS3MJSOwkFbFirjccjHmxMJ3MPUXHck0ZmmC CEC0B9gWmdvrkyKh2bvSkw8/GzmYRi/3H1LVnQE4KO96KwNcvnLwPYqkFhQMAYNt79NjRqww2tf zCUFm0/3yti9RG2XX4h+xfKrz/1g= X-Google-Smtp-Source: AGHT+IHzVL7LBFGV36FWLNcpSg2orLPp1ASVn+mbEDBbCkc4h0hJ2ubze1gy8s0MLbB0Ujsgd9CuN+cHxObWiCWjNb8= X-Received: by 2002:a05:6808:1827:b0:3e6:329e:adb2 with SMTP id 5614622812f47-3e794698bf2mr19312142b6e.11.1731548187909; Wed, 13 Nov 2024 17:36:27 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a05:6802:27c2:b0:56c:c9af:3ee6 with HTTP; Wed, 13 Nov 2024 17:36:27 -0800 (PST) In-Reply-To: <3BA7883C-2247-4687-A764-5777EB8755EF@mophilly.com> References: <3BA7883C-2247-4687-A764-5777EB8755EF@mophilly.com> From: "David G. Johnston" Date: Wed, 13 Nov 2024 18:36:27 -0700 Message-ID: Subject: Re: Row level security policy To: Mark Phillips Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000a6e7a60626d57a81" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a6e7a60626d57a81 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, November 13, 2024, Mark Phillips wrote: > Given a database table with one policy statement FOR SELECT applied, it i= s > necessary to apply additional policy statements for insert, update, and > delete operations? > It isn=E2=80=99t necessary but most conventional use cases would involve establishing policies for writing as well as reading. But it is use case dependent. David J. --000000000000a6e7a60626d57a81 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, November 13, 2024, Mark Phillips <mphillips@mophilly.com> wrote:
Given a database table with one policy statement FOR SELECT = applied, it is necessary to apply additional policy statements for insert, = update, and delete operations?

It isn=E2=80=99t necessary but most conven= tional use cases would involve establishing policies for writing as well as= reading.=C2=A0 But it is use case dependent.

Davi= d J.

--000000000000a6e7a60626d57a81--