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 1tBPMs-003dJ0-Jb for pgsql-general@arkaria.postgresql.org; Thu, 14 Nov 2024 02:13:57 +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 1tBPMp-000Mtm-DZ for pgsql-general@arkaria.postgresql.org; Thu, 14 Nov 2024 02:13:55 +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 1tBPMp-000Mtd-1t for pgsql-general@lists.postgresql.org; Thu, 14 Nov 2024 02:13:55 +0000 Received: from mail.narocalifornia.org ([206.214.166.96] helo=mophilly.com) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tBPMi-001oNu-9n for pgsql-general@lists.postgresql.org; Thu, 14 Nov 2024 02:13:54 +0000 Received: (qmail 26365 invoked by uid 453); 14 Nov 2024 02:13:46 -0000 X-Virus-Checked: by ClamAV 0.103.11 on mophilly.com X-Virus-Found: No Authentication-Results: mophilly.com; auth=pass (plain) smtp.auth=mphillips Received: from wsip-98-173-51-151.sd.sd.cox.net (HELO smtpclient.apple) (98.173.51.151) by mophilly.com (qpsmtpd/0.96) with ESMTPSA (ECDHE-RSA-AES256-GCM-SHA384 encrypted); Wed, 13 Nov 2024 18:13:46 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=mophilly.com; h=content-type:content-transfer-encoding:from:mime-version:subject:date:message-id:references:cc:in-reply-to:to; s=default; bh=8fifkPD+bzs2TiKCtbLWwl2MdBhjh+xH9mnbGkErazs=; b=MXs6SDHd+adox5NyRiBe6Kd5kEvBvWyQ+b/OH52R0CBGg2XxpJCsyA1q4p/3DDSVRq2rS3T+N3DPMN6GlL9XiMIABgCTn7R1qUPetkx4kecNmgMzPbA3xTpQpm9ZY5HyD9VAgECSRA7aw64QRW7exHW/jSE6j9fIhxelaA3fwrKi1iDSxOA9U9cTLWZNpCwMcIQqO/dFBam7rF+FqFPedZOz4r89RgXsFuVH7RvYhpX9a1hZqdlVTmNC/QU/RViLsFhINo4hfnMy9FxFxdg7XzHjBZaIg6xINwqQBuV7EDmtdJeNEq+wkX+Ir3U+IBcwXfjSZDLzF5hI/iyIlM1vCg== Content-Type: multipart/alternative; boundary=Apple-Mail-85E717FE-9172-4FCD-8EB8-06CF7BE2C29A Content-Transfer-Encoding: 7bit From: Mark Phillips Mime-Version: 1.0 (1.0) Subject: Re: Row level security policy Date: Wed, 13 Nov 2024 18:13:24 -0800 Message-Id: <3D0A30B0-0A39-4F71-9449-415196B631DE@mophilly.com> References: Cc: pgsql-general@lists.postgresql.org In-Reply-To: To: "David G. Johnston" X-Mailer: iPad Mail (22A3370) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail-85E717FE-9172-4FCD-8EB8-06CF7BE2C29A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thank you. I will revisit my test cases to b= e sure I have the use cases covered.

- Mark, out and about.

<= blockquote type=3D"cite">On Nov 13, 2024, at 5:36=E2=80=AFPM, David G. Johns= ton <david.g.johnston@gmail.com> wrote:

=EF=BB=BFOn Wednesday, November 13, 2= 024, Mark Phillips <mphillips@m= ophilly.com> wrote:

Given a database= table with one policy statement FOR SELECT applied, it is necessary to appl= y additional policy statements for insert, update, and delete operations?

It isn=E2=80=99t necessary but most convent= ional use cases would involve establishing policies for writing as well as r= eading. But it is use case dependent.

David J= .

= --Apple-Mail-85E717FE-9172-4FCD-8EB8-06CF7BE2C29A--