Re: Support for REINDEX CONCURRENTLY
От | Andres Freund |
---|---|
Тема | Re: Support for REINDEX CONCURRENTLY |
Дата | |
Msg-id | 20130303125436.GA13803@alap2.anarazel.de обсуждение исходный текст |
Ответ на | Re: Support for REINDEX CONCURRENTLY (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: Support for REINDEX CONCURRENTLY
|
Список | pgsql-hackers |
On 2013-03-01 16:32:19 -0500, Peter Eisentraut wrote: > REINDEX CONCURRENTLY resets the statistics in pg_stat_user_indexes, > whereas plain REINDEX does not. I think they should be preserved in > either case. Yes. Imo this further suggests that it would be better to switch the relfilenodes (+indisclustered) of the two indexes instead of switching the names. That would allow to get rid of the code for moving over dependencies as well. Given we use an exclusive lock for the switchover phase anyway, there's not much point in going for the name-based switch. Especially as some eventual mvcc-correct system access would be fine with the relfilenode method. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: