| From: | solai v <solai(dot)cdac(at)gmail(dot)com> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY FROM with RLS |
| Date: | 2026-05-25 04:50:37 |
| Message-ID: | CAF0whudLobRaqg=hk0w_3+OYYxo-fBAS3zDdiBOE4WAAGMRP9g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi jian,
I tested the v2 patch for COPY FROM with RLS.
Before applying the patch, I was able to reproduce the issue where
\copy bypassed the RLS INSERT policy and allowed invalid rows to be
inserted.
After applying the patch and retesting, rows violating the policy were
correctly rejected during \copy, while valid rows were inserted
successfully. The behavior is now consistent with normal INSERT.
The error context reporting during COPY was also clear and helpful
while testing.
Regards,
Solai
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Japin Li | 2026-05-25 05:20:57 | Re: pg_rewind does not rewind diverging timelines |
| Previous Message | vignesh C | 2026-05-25 04:42:53 | Re: Proposal: Conflict log history table for Logical Replication |