3 ms·
How massive of an undertaking is this going to be? There is a mention they think they could get it done in 1-2 releases. https://pgpedia.info/postgresql-version
by MuffinFlavored 3y ago
How massive of an undertaking is this going to be? There is a mention they think they could get it done in 1-2 releases. https://pgpedia.info/postgresql-versions/index.html https://pgpedia.info/postgresql-versions/index.html they seem to release once a year from what I can deduct. 1-2 years, not bad. I wonder how many people would work on this (full time/part time) and how many resource hours would go into this.
I wonder which layer would benefit the most.
You connect as pg_client to pg_server, you make a request (SQL query). It has to get tokenized/query planned, then probably some detection layer that already exists that says "do this all in a single thread or spread it across multiple". How does a single threaded process that spawns multiple threads -> a multi-threaded process benefit in these situations given the overhead of having to sync/message in between threads messages back and forth?
- Icathian 3y agoPostgres in particular has many other processes that do a ton of bookkeeping and maintenance. Autovacuum, checkpointer, walwriter, etc. Each of these having process overhead and also having to deal with shared memory is probably the target of this proposal if I had to guess.
- tristan957 3y agoThis proposal is more concerned with each connection being its own process. I think the current thoughts are to keep utility processes around.