Skip site navigation (1) Skip section navigation (2)

update, truncate and vacuum

From: Scott Feldstein <scott(dot)feldstein(at)hyperic(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: update, truncate and vacuum
Date: 2007-07-26 22:36:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
I have a couple questions about how update, truncate and vacuum would  
work together.

1) If I update a table foo (id int, value numeric (20, 6))
update foo set value = 100 where id = 1

Would a vacuum be necessary after this type of operation since the  
updated value is a numeric? (as opposed to a sql type where its size  
could potentially change i.e varchar)

2) After several updates/deletes to a table, if I truncate it, would  
it be necessary to run vacuum in order to reclaim the space?



pgsql-performance by date

Next:From: Dave DutcherDate: 2007-07-26 22:59:58
Subject: Re: update, truncate and vacuum
Previous:From: Jignesh K. ShahDate: 2007-07-26 21:17:55
Subject: Re: User concurrency thresholding: where do I look?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group