| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parallel query execution |
| Date: | 2013-01-17 01:04:05 |
| Message-ID: | CAMkU=1w675xakacASACWXyqcfVv1iDwKCJNu75fzO+WU_Dg_Zw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tuesday, January 15, 2013, Stephen Frost wrote:
> * Gavin Flower (GavinFlower(at)archidevsys(dot)co(dot)nz <javascript:;>) wrote:
> > How about being aware of multiple spindles - so if the requested
> > data covers multiple spindles, then data could be extracted in
> > parallel. This may, or may not, involve multiple I/O channels?
>
> Yes, this should dovetail with partitioning and tablespaces to pick up
> on exactly that.
I'd rather not have the benefits of parallelism be tied to partitioning if
we can help it. Hopefully implementing parallelism in core would result in
something more transparent than that.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2013-01-17 01:05:16 | Re: review: pgbench - aggregation of info written into log |
| Previous Message | Andrew Dunstan | 2013-01-17 00:48:46 | Re: review: pgbench - aggregation of info written into log |