3 ms·
I think my bigger fear is around security. A process per connection keeps things pretty secure for that connection regardless of what the global variables are
by cogman10 3y ago
I think my bigger fear is around security. A process per connection keeps things pretty secure for that connection regardless of what the global variables are doing (somewhat hard to mess that up with no concurrency going on in a process).
Merge all that into one process with many threads and it becomes a nightmare problem to ensure some random addon didn't decide to change a global var mid processing (which causes wrong data to be read).
- dfox 3y agoAll postgres processes run under the same system user and all the access checking happens completely in userspace.
- fdr 3y agoAccess checking, yes, but the scope of memory corruption does increase unavoidably, given the main thing the pgsql-hackers investigating threads want: one virtual memory context when toggling between concurrent work. Of course, there's a huge amount of shared space already, so a willful corruption can already do virtually anything. But, more is more.