Re: [HACKERS] Urgent Help Required - Mailing list pgsql-general

From Kevin Grittner
Subject Re: [HACKERS] Urgent Help Required
Date
Msg-id 1381411417.59052.YahooMailNeo@web162901.mail.bf1.yahoo.com
Whole thread Raw
In response to Re: [HACKERS] Urgent Help Required  (Chris Travers <chris.travers@gmail.com>)
List pgsql-general
Chris Travers <chris.travers@gmail.com> wrote:
> John R Pierce <pierce@hogranch.com> wrote:

> I often find in those cases it is a choice between vacuum full
> and dumpall/initdb/reload/analyze.....

Way back in the 8.1 days I often found CLUSTER to be my best option
-- as long as I had room enough for a second copy (without the
bloat) while it was running.  If I didn't have that much room the
dump/initdb/restore option was almost always faster than VACUUM
FULL.  Personally, I would follow the restore with VACUUM FREEZE
ANALYZE rather than just ANALYZE, so that the entire database
didn't come due for wraparond prevention vacuums at an inopportune
time.

The main thing here seem to be to upgrade to a supported version
(preferably 9.2 or 9.3).

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-general by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Tree structure
Next
From: Attila Soki
Date:
Subject: Feature request: support queries with returning on simple views with automatic update