Re: impact of truncate table on indexes
| От | Tom Lane |
|---|---|
| Тема | Re: impact of truncate table on indexes |
| Дата | |
| Msg-id | 17582.1324579222@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | impact of truncate table on indexes (Dinesh Bhandary <dbhandary@iii.com>) |
| Список | pgsql-admin |
Dinesh Bhandary <dbhandary@iii.com> writes: > We have been having some performance issues with indexes right after > truncating a table. You'd need to be a lot more specific than that if you want useful help. Also, pgsql-performance is a better list for discussing performance issues. http://wiki.postgresql.org/wiki/SlowQueryQuestions > My understanding is truncate removes all the > contents of the table and the space get reclaimed immediately. > In such cases what happens to its indexes. They get rebuilt as empty indexes. > It does not seem like they > are removed, but merely marked for deletion by a vacuum job and it > creates huge bloats and performance problems. On what do you base this clearly-contrary-to-reality conclusion? regards, tom lane
В списке pgsql-admin по дате отправления: