[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-admin
Subject:    Re: [ADMIN] impact of truncate table on indexes
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2011-12-22 18:40:22
Message-ID: 17582.1324579222 () sss ! pgh ! pa ! us
[Download RAW message or body]

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

-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
[prev in list] [next in list] [prev in thread] [next in thread]