Re: Parallel query execution
| От | Michael Paquier |
|---|---|
| Тема | Re: Parallel query execution |
| Дата | |
| Msg-id | CAB7nPqSnwdE-FNinbpSvAz2pwtgNQ4e+9MJOJEZRQ+AtrGoTWQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Parallel query execution (Bruce Momjian <bruce@momjian.us>) |
| Ответы |
Re: Parallel query execution
|
| Список | pgsql-hackers |
On Wed, Jan 16, 2013 at 1:32 PM, Bruce Momjian <bruce@momjian.us> wrote:
Michael PaquierOn Wed, Jan 16, 2013 at 01:28:18PM +0900, Michael Paquier wrote:We have that in pg_restore, and I thinnk we are getting parallel dump in
>
>
> On Wed, Jan 16, 2013 at 1:22 PM, Josh Berkus <josh@agliodbs.com> wrote:
>
> Claudio, Stephen,
>
> It really seems like the areas where we could get the most "bang for the
> buck" in parallelism would be:
>
> 1. Parallel sort
> 2. Parallel aggregation (for commutative aggregates)
> 3. Parallel nested loop join (especially for expression joins, like GIS)
>
> parallel data load? :/
9.3, right? Unfortunately, I don't see it in the last 9.3 commit-fest.
Is it still being worked on?
Not exactly, I meant something like being able to use parallel processing when doing INSERT or COPY directly in core. If there is a parallel processing infrastructure, it could also be used for such write operations. I agree that the cases mentioned by Josh are far more appealing though...
--
--
http://michael.otacoo.com
В списке pgsql-hackers по дате отправления: