Re: Parallel tuplesort (for parallel B-Tree index creation)
| От | Alvaro Herrera |
|---|---|
| Тема | Re: Parallel tuplesort (for parallel B-Tree index creation) |
| Дата | |
| Msg-id | 20161204014544.55snjukv3xcuesyb@alvherre.pgsql обсуждение исходный текст |
| Ответ на | Re: Parallel tuplesort (for parallel B-Tree index creation) (Peter Geoghegan <pg@heroku.com>) |
| Ответы |
Re: Parallel tuplesort (for parallel B-Tree index creation)
|
| Список | pgsql-hackers |
Peter Geoghegan wrote: > On Mon, Nov 7, 2016 at 8:28 PM, Peter Geoghegan <pg@heroku.com> wrote: > > What do we need to teach pg_restore about parallel CREATE INDEX, if > > anything at all? Could this be as simple as a blanket disabling of > > parallelism for CREATE INDEX from pg_restore? Or, does it need to be > > more sophisticated than that? I suppose that tools like reindexdb and > > pgbench must be considered in a similar way. > > I still haven't resolved this question, which seems like the most > important outstanding question, I don't think a patch must necessarily consider all possible uses that the new feature may have. If we introduce parallel index creation, that's great; if pg_restore doesn't start using it right away, that's okay. You, or somebody else, can still patch it later. The patch is still a step forward. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: