pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Chao Li <li.evan.chao@gmail.com>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Paul A Jungwirth <pj@illuminatedcomputing.com>
Cc: Dean Rasheed <dean.a.rasheed@gmail.com>
Cc: Ayush Tiwari <ayushtiwari.slg01@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows
Date: Mon, 20 Jul 2026 14:59:51 +0800
Message-ID: <174C770E-07C8-4400-AC80-A46BFC2B68DD@gmail.com> (raw)
In-Reply-To: <a1e965bc-01c0-47cd-8588-4cb3e60a1184@eisentraut.org>
References: <6C34A987-AC50-4477-BD71-2D4AFEE1A589@gmail.com>
	<CAJTYsWWJeKKY=Db3R2yP7X8CeHoEu1tFcrRHKRgAf4Fv5-P11g@mail.gmail.com>
	<07EF5F4D-4AA3-4C21-8868-9ACC0D8B6655@gmail.com>
	<B4648790-5945-4C73-AF5A-8CE8A812527E@gmail.com>
	<CA+renyWnvqWPPdfvV1GmGr9wzG5S6c3Th=gpn2ShN0RLhR-Fsg@mail.gmail.com>
	<CA+renyWYcQ=Yc1zQJ2UzLDF2cdHBHto-dRHw9s9EAA111ApEqQ@mail.gmail.com>
	<20DF964A-C291-491A-9126-62753DCBD7CE@gmail.com>
	<CA+renyU=1A7+_zyPdaa6TersUDPrX13ufDW-qdi1wGt_zxXCfA@mail.gmail.com>
	<CAEZATCWEsMTVTA4mOPidvPE4wEv=oVzurR+vSAPmeT4RS7FqCg@mail.gmail.com>
	<CA+renyX5Mk7oq-S2eX1q7656ThtynmN5J9TWp2fSvWuMPivPjA@mail.gmail.com>
	<CAEZATCXW3O9_cniVFtw76zFO5p9D06P1bwMvG8RU4_YFkm0iwA@mail.gmail.com>
	<CA+renyWqKvB86R2FBAUh=AWoyt40qMf7yHWzoHaBr15kyy+Tjw@mail.gmail.com>
	<49247968-DB60-4FF3-892F-CF910E63ADBA@gmail.com>
	<CA+renyX3xny=og54iiOcVe0C0kLqEX+4cBg4cF-odE9eXN_8QA@mail.gmail.com>
	<a1e965bc-01c0-47cd-8588-4cb3e60a1184@eisentraut.org>



> On Jul 20, 2026, at 14:53, Peter Eisentraut <peter@eisentraut.org> wrote:
> 
> On 16.07.26 17:35, Paul A Jungwirth wrote:
>> On Wed, Jul 15, 2026 at 6:10 PM Chao Li <li.evan.chao@gmail.com> wrote:
>>> 
>>> Actually, when I received v4, I was also working on addressing Dean’s comments.
>>> 
>>> I reviewed both v4 and v5, made some small adjustments, and here is v6:
>>> 
>>> * For the create_policy doc change, I changed “check new row” to “check leftover rows”.
>>> * For the “SELECT rights” comment, I moved it into the block comment, because its position in v5 looked like a placeholder.
>>> * For the tests, v4 and v5 added the new cases in the MERGE section. I added the test in a more direct section.
>>> * For the tests, v4 and v5 granted INSERT privilege. V6 intentionally does not, because the test runs UPDATE/DELETE FOR PORTION OF, and INSERT privilege is not required for inserting leftover rows by design.
>> I took a look. These all seem like improvements to me.
> 
> committed v6

Thanks for committing.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/










view thread (17+ messages)

Message-ID: <174C770E-07C8-4400-AC80-A46BFC2B68DD@gmail.com>
Permalink:  ../174C770E-07C8-4400-AC80-A46BFC2B68DD@gmail.com/
Also on:    postgresql.org/message-id/174C770E-07C8-4400-AC80-A46BFC2B68DD@gmail.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: li.evan.chao@gmail.com, peter@eisentraut.org, pj@illuminatedcomputing.com, dean.a.rasheed@gmail.com, ayushtiwari.slg01@gmail.com
  Subject: Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows
  In-Reply-To: <174C770E-07C8-4400-AC80-A46BFC2B68DD@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox