Re: Support for REINDEX CONCURRENTLY
| От | Michael Paquier |
|---|---|
| Тема | Re: Support for REINDEX CONCURRENTLY |
| Дата | |
| Msg-id | CAB7nPqQOfCLFcQPS_ecUMDF3dueFinkbayHvx4NtaSEu_+8otg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Support for REINDEX CONCURRENTLY (Fujii Masao <masao.fujii@gmail.com>) |
| Ответы |
Re: Support for REINDEX CONCURRENTLY
|
| Список | pgsql-hackers |
On Thu, Jul 4, 2013 at 3:26 AM, Fujii Masao <masao.fujii@gmail.com> wrote: > On Thu, Jul 4, 2013 at 2:41 AM, Fujii Masao <masao.fujii@gmail.com> wrote: >> On Thu, Jul 4, 2013 at 2:36 AM, Andres Freund <andres@2ndquadrant.com> wrote: >>> On 2013-07-04 02:32:32 +0900, Michael Paquier wrote: >>>> > Wouldn't it make more sense to fetch the toast index oid in the query >>>> > ontop instead of making a query for every relation? >> >> +1 >> I changed the query that way. Updated version of the patch attached. >> >> Also I updated the rules.out because Michael changed the system_views.sql. >> Otherwise, the regression test would fail. >> >> Will commit this patch. > > Committed. So, let's get to REINDEX CONCURRENTLY patch! Thanks for the hard work! I'll work on something based on MVCC catalogs, so at least lock will be lowered at swap phase and isolation tests will be added. -- Michael
В списке pgsql-hackers по дате отправления: