Re: Bug: RLS policy FOR SELECT is used to check new rows - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Bug: RLS policy FOR SELECT is used to check new rows
Date
Msg-id 62c73a97e607ce46b989f8950c4ba3bc8c0d0535.camel@j-davis.com
Whole thread Raw
In response to Re: Bug: RLS policy FOR SELECT is used to check new rows  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bug: RLS policy FOR SELECT is used to check new rows
List pgsql-hackers
On Tue, 2023-10-24 at 11:59 -0400, Tom Lane wrote:
> I'm fairly sure that it was intentional, but I don't recall the
> reasoning; perhaps Stephen does.  In any case, I grasp your point
> that maybe we should distinguish RETURNING from not-RETURNING cases.

Perhaps the idea is that if there are constraints involved, the failure
or success of an INSERT/UPDATE/DELETE could leak information that you
don't have privileges to read.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock
Next
From: Robert Haas
Date:
Subject: Re: Bug: RLS policy FOR SELECT is used to check new rows