3 ms·
Not a 100% technically correct answer most likely but first look suggests they hook into the statement preprocessing pipeline. In the example, they’re hooking i
by rad_gruchalski 5y ago
Not a 100% technically correct answer most likely but first look suggests they hook into the statement preprocessing pipeline. In the example, they’re hooking into the ALTER ROLE statement and deny execution if the role is a protected one. I don’t think this can be done with triggers without creating triggers on system tables and knowing the exact places where postgres would try to make changes. This seems to be an ott solution and probably a pretty bulletproof one.
Very timely article, I wonder if this works with yugabyte...
- steve-chavez 5y ago> I wonder if this works with yugabyte It should work too! Check this line here[1]. That shows that Yugabyte also has the `ProcessUtility_hook`(same one used in the article) defined. It would be a matter of installing and loading the Supautils extension. [1]: https://github.com/yugabyte/yugabyte-db/blob/master/src/postgres/src/backend/tcop/utility.c#L373-L376 https://github.com/yugabyte/yugabyte-db/blob/master/src/post...
- rad_gruchalski 5y agoI’ll give it a shot over the weekend as I have a few use cases for similar functionality in Yugabyte. This is pretty exciting stuff at the right time!