Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by dprkh on Thursday November 12, 2026 @11:31PM
(#50478354)
Why use SQL for authentication and authorization? I understand that the point of SQL is so that the query optimizer can create an efficient execution plan, but there is no need for that when it comes to configuring auth, right?
[ Parent
| on HN ]
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by simcop2387 on Thursday November 12, 2026 @11:42PM
(#50478445)
It can severely simplify a lot of patterns like row level security and other things inside the database that need tigher access controls.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by jamesfinlayson on Friday November 13, 2026 @01:02AM
(#50478962)
I think at my day job it's used so that a bunch of things can connect to the production database to siphon off data for BI/do ancillary tasks (owned by other teams) without messing anything up, while the main business application that actually writes to the database has the ability to do pretty much everything.