| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Subject: | Re: vacuum error |
| Date: | 2007-03-07 10:13:35 |
| Message-ID: | 20070307101335.GC1482@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Mar 07, 2007 at 02:29:08AM -0700, Ed L. wrote:
> Perhaps my question was not clear enough. Let me rephrase: Does
> the fix for this problem comes from a *fresh* DB structure
> resulting from the initdb, or from a software fix in 8.1.8, or
> both? The answer makes a big difference with a 200gb database.
> If it's in the software alone, we can simply restart. If it's
> in the DB structure, we have to migrate 200gb of data from one
> PGDATA to another.
It would come from upgrading the software. Reinitdbing won't actually
make a difference. The whole point of minor versions is that you don't
need to reinit the DB, otherwise it'd be a major version...
In your case you could also get running by creating the missing file,
but whether that's appropriate depends on the cause. I'd check the
release notes to see if any related bugs have been fixed since then.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Elgert | 2007-03-07 11:12:52 | Re: postgres slower on nested queries |
| Previous Message | Ed L. | 2007-03-07 09:29:08 | Re: vacuum error |