On Mon, 2 Jun 2025 at 22:52, jian he <jian.universal...@gmail.com> wrote:
Do we consider INSERT associated with user defined function a security > bug? for > example, the following, INSERT with a check constraint. > [....] If so, then it's a very old issue... > A very old issue for INSERT/UPDATE/DELETE, but until this patch not an issue for SELECT from a table (although if I understand correctly earlier discussion SELECT from a view can already be a problem). That being said I would like to see it corrected everywhere. My fix would be for check constraints, triggers, and view definitions to run as the owner of the object in question (constraint, trigger, or view or materialized view), essentially using the same facility as used to run security definer functions. Then, as an optimization only, skip actually doing the security definer stuff (which I understand to be slow) when it can be proven by the planner to be safe to do so (i.e., no difference in result). Of course in just a few sentences I proposed a research project that could probably generate dozens of PhD theses, and I'm not volunteering to do any of this at least not in the near future. But I hope I made clear what is different about this proposal from the existing situation.
