Re: [HACKERS] Urgent Help Required

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Chris Travers <chris(dot)travers(at)gmail(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: [HACKERS] Urgent Help Required
Date: 2013-10-10 13:23:37
Message-ID: 1381411417.59052.YahooMailNeo@web162901.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Chris Travers <chris(dot)travers(at)gmail(dot)com> wrote:
> John R Pierce <pierce(at)hogranch(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Attila Soki 2013-10-10 13:40:13 Feature request: support queries with returning on simple views with automatic update
Previous Message Merlin Moncure 2013-10-10 13:21:36 Re: Tree structure

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2013-10-10 13:25:39 Re: PSQL return coder
Previous Message Andres Freund 2013-10-10 13:23:30 Re: space reserved for WAL record does not match what was written: panic on windows