| From: | "Khan, Tanzeel" <tzlkhan(at)amazon(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Remove redundant comment regarding RelationBuildRowSecurity in relcache.c |
| Date: | 2025-04-28 13:27:48 |
| Message-ID: | 8BD3D145-D880-49B9-9A5D-09EDEF5CEF4A@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
A comment in relcache.c mentions that RelationBuildRowSecurity
adds a default-deny policy when no policy exists on table. This
does not seem to be the case. The default deny policy is added
later on, inside get_row_security_policies(). Also it mentions that
there can never be zero policies for a relation which is true
but here it kind of hints that rd_rsdesc->policies can never be
null.
Added a patch to remove both of these comments.
Thanks,
Tanzeel Khan
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Remove-redundant-comment-about-RelationBuildRowSecur.patch | application/octet-stream | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-04-28 14:27:20 | Re: Restrict publishing of partitioned table with a foreign table as partition |
| Previous Message | Tom Lane | 2025-04-28 13:14:54 | Re: allow changing autovacuum_max_workers without restarting |