From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: vacuum full 100 mins plus?
Date: Wed, 14 Jul 2004 22:21:29 -0400
Message-ID: <m33c3uhuxi.fsf@wolfe.cbbrowne.com> (raw)
References: <OF3581B09F.CDD98B1C-ON88256ED1.007318CA-88256ED1.0076E70C@fds.com>
<OFE37D67EB.C42A1B3B-ON88256ED1.007C0430-88256ED1.007D08AB@fds.com>
A long time ago, in a galaxy far, far away, PHatcher@macys.com (Patrick Hatcher) wrote:
> Answered my own question. I gave up the vacuum full after 150 mins. I was
> able to export to a file, vacuum full the empty table, and reimport in less
> than 10 mins. I suspect the empty item pointers and the sheer number of
> removable rows was causing an issue.
In that case, you'd be a little further better off if the steps were:
- drop indices;
- copy table to file (perhaps via pg_dump -t my_table);
- truncate the table, or drop-and-recreate, both of which make
it unnecessary to do _any_ vacuum of the result;
- recreate indices, probably with SORT_MEM set high, to minimize
paging to disk
- analyze the table (no need to vacuum if you haven't created any
dead tuples)
- cut SORT_MEM back down to "normal" sizes
--
output = reverse("gro.gultn" "@" "enworbbc")
http://www3.sympatico.ca/cbbrowne/spreadsheets.html
Signs of a Klingon Programmer #6: "Debugging? Klingons do not
debug. Our software does not coddle the weak."
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: cbbrowne@acm.org
Subject: Re: vacuum full 100 mins plus?
In-Reply-To: <m33c3uhuxi.fsf@wolfe.cbbrowne.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox