16 comments

[ 5.0 ms ] story [ 55.5 ms ] thread
Can someone explain to me (and others) a potential usecase for this ?
Intra-query parallelism for starters.
(comment deleted)
Will this be compatible with say pg_shard?

Does anyone know how this stacks up against CitusDB?

Is the target for Postgres to natively do what CitusDB does right now?

This is about parallelism on a single machine.
Are there any examples how to use this feature?
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_W5wR4Hi...

Thanks 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 :)
It'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.
We might see parallel seqscan soon.
Yeah, I think this is all under the hood, so in future releases, Postgres should perform even better for you ;)