vacuum after truncate - Mailing list pgsql-performance

From Mariel Cherkassky
Subject vacuum after truncate
Date
Msg-id CA+t6e1=Xid-2j562k3J=-WKsYARt0STXBFT9ephcvMUo9NAQbQ@mail.gmail.com
Whole thread Raw
Responses Re: vacuum after truncate
List pgsql-performance
Hi, I have a big function that includes many truncates on different tables. In the documentation is is written that truncates creates a new file and resign the old filenode to the new filenode and the old file (old data of the table) is deleted in commit. In order to execute my function I run psql -d 'aa' -U 'bb' -C "select function()"; I have a few questions about it ? 1.When I start the function, it means that the whole function is one big transaction right ? 2..Because the truncates I preform are part of a transaction it means that only at the end of the transaction that space will be freed ? Which mean only when the function is finished? 3..Does running vacuum at the end of the function on the tables that were truncated and then populated with data will have any impact or is it better just to analyze them ? Thanks.

pgsql-performance by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Bitmap scan is undercosted? - boolean correlation
Next
From: Laurenz Albe
Date:
Subject: Re: vacuum after truncate