[GENERAL] TRUNCATE - timing of the return of disk space - caused by long-lived client?

Hi All, Running postgres 8.1.9 on SLES10 (kernel 2.6.16) currently, I noticed something about the behaviour of TRUNCATE on a large table. The docs imply that TRUNCATE is the best way to delete everything in a table (rather than DELETE) since there is no need to VACUUM afterward - the disk space

Re: [GENERAL] TRUNCATE - timing of the return of disk space - caused by long-lived client?

filehandle. Thanks for the pointers. Vince -Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: 26 October 2007 13:22 To: Vince Negri Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] TRUNCATE - timing of the return of disk space - caused by long-lived client