Re: vacuum vs pg_repack for clearing bloat?

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: vacuum vs pg_repack for clearing bloat?
Date: 2014-01-16 01:33:19
Message-ID: 52D736DF.7080301@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Lists 2014-01-16 01:37:27 Re: vacuum vs pg_repack for clearing bloat?
Previous Message Andrew Sullivan 2014-01-16 01:12:15 Re: vacuum vs pg_repack for clearing bloat?