8 ms·
Note that this in itself is not a feature but part of the infrastructure for developing parallel execution nodes (for an example, you could take a look at paral
by amitlan 11y ago
Note that this in itself is not a feature but part of the infrastructure for developing parallel execution nodes (for an example, you could take a look at parallel seq scan under development[1])
EDIT: [1] is a huge discussion, by the way.
[1] http://www.postgresql.org/message-id/CAA4eK1KTv73uD9_W5wR4HiMZ_hgi8oseWncxbC53XwZDp-8aEg@mail.gmail.com http://www.postgresql.org/message-id/CAA4eK1KTv73uD9_W5wR4Hi...
- onderkalaci 11y agoThanks for the reply. Then, my question becomes as follows: Is there a way for basic PostgreSQL users (as me) benefit from this (yet)? I don't want to dive into any codes :)
- JonnieCache 11y agoIt's a framework for future functionality. End-users won't be touching it for some time I expect. The best thing about psql is their careful, iterative engineering.
- amitlan 11y agoWe might see parallel seqscan soon.
- netghost 11y agoYeah, I think this is all under the hood, so in future releases, Postgres should perform even better for you ;)