Re: vacuum vs pg_repack for clearing bloat? - Mailing list pgsql-general

From John R Pierce
Subject Re: vacuum vs pg_repack for clearing bloat?
Date
Msg-id 52D736DF.7080301@hogranch.com
Whole thread Raw
In response to vacuum vs pg_repack for clearing bloat?  (Lists <lists@benjamindsmith.com>)
List pgsql-general
On 1/15/2014 4:09 PM, Lists wrote:
> Our app makes extensive use of temp tables, and this causes a
> significant amount of bloat that can often only be cleared with a
> manual vacuum process.

whats the persistence of these temporary tables?    by design, they are
meant for relatively short lifespan uses, and as Tom said are only
accessible by the connection that created them, and when you're done
with them you should drop them.

now, if you mean 'temporary table' in another sense, like regular tables
you're using for storing temporary data, how are you cleaning this
'temporary data' out of them?    truncate should free the disk space
they use where delete won't.


--
john r pierce                                      37N 122W
somewhere on the middle of the left coast



pgsql-general by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: vacuum vs pg_repack for clearing bloat?
Next
From: Lists
Date:
Subject: Re: vacuum vs pg_repack for clearing bloat?