Skip site navigation (1) Skip section navigation (2)

Re: best way to run maintenance script

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Vinubalaji Gopal" <vgopal(at)abaca(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Pgsql-Performance \(\(E-mail\)\)" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: best way to run maintenance script
Date: 2008-03-15 12:46:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
"Vinubalaji Gopal" <vgopal(at)abaca(dot)com> writes:

> On Fri, 2008-03-14 at 18:37 -0700, Tom Lane wrote:
>> That's only a little bit better.  Read about all the bug fixes you're
> Sure - will eventually upgrade it sometime - but it has to wait for
> now :(

Waiting for one of those bugs to bite you is a bad plan.

We're not talking about an upgrade to 8.1, 8.2, or 8.3. We're talking about
taking bug-fixes and security fixes for the release you're already using.

Normally it's just a shutdown and immediate restart. There are exceptions
listed in the 8.0.6 release notes which would require a REINDEX but they don't
affect most people.

  Gregory Stark
  Ask me about EnterpriseDB's PostGIS support!

In response to

pgsql-performance by date

Next:From: RichDate: 2008-03-16 06:11:48
Subject: What is the best way to storage music files in Postgresql
Previous:From: Vinubalaji GopalDate: 2008-03-15 05:07:45
Subject: Re: best way to run maintenance script

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group