On Thu, May 17, 2018 at 10:42:00PM -0700, Andres Freund wrote: > > We also have what seems like half an OS worth of tooling to support our > > shared-nothing-by-default multi-processing model. Custom spinlocks, our > > LWLocks, our latches, signal based IPC + ProcSignal signal multiplexing, > > extension shmem reservation and allocation, DSM, DSA, longjmp based > > exception handling and unwinding ... the learning curve for PostgreSQL > > programming is a whole lot more than just C even before you get into the > > DB-related bits. And there's not a great deal of help with the learning > > curve. > > A good chunk of that we'd probably have anyway. Even with threads we'd > likely have our own spinlocks, lwlocks, latches, signal handling, > explict shared memory (for hugepages). I think having a decently > performant DB will always imply a lot of "OS like" infrastructure. >
I think threading would definitely make server programming harder. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +