Re: more than one index in a single heap pass?
От | Bruce Momjian |
---|---|
Тема | Re: more than one index in a single heap pass? |
Дата | |
Msg-id | 200907151445.n6FEjuT23471@momjian.us обсуждение исходный текст |
Ответ на | Re: more than one index in a single heap pass? (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: more than one index in a single heap pass?
|
Список | pgsql-hackers |
Andrew Dunstan wrote: > > Wasn't that a big part of the point of the "parallel pg_restore" feature? > > > > > > Well, yes, it's some of it, and in theory Tom's late addition of a queue > that gets all the dependencies of a table as soon as the table data is > restored should make that work better. But of course, that's not the > only time indexes are created, and each index creation command will be > doing its own heap processing, albeit that synchronised scanning will > make that lots cheaper. > > As I said originally, it was just an idle thought that came to me today. Well, TODO has: Allow multiple indexes to be created concurrently, ideally via asingle heap scan, and have pg_restore use it Isn't this already largely done by parallel pg_restore work? so we have to decide if we still want that item. I think what we don't have is a way to create multiple indexes simultaneously via SQL. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-hackers по дате отправления: