| From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Subject: | Re: vacuum error |
| Date: | 2007-03-07 09:29:08 |
| Message-ID: | 200703070229.08796.pgsql@bluepolka.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tuesday March 6 2007 11:52 pm, Peter Eisentraut wrote:
> Ed L. wrote:
> > Right. I'm asking if the fix for this problem is in the new
> > 8.1.8 software, or in the new DB structure resulting from
> > the initdb, or perhaps both.
>
> There is no new DB structure in 8.1.8, which is why you can
> update without initdb. Consult the release notes for details.
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.
Ed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2007-03-07 10:13:35 | Re: vacuum error |
| Previous Message | Richard Huxton | 2007-03-07 09:16:53 | Re: postgres slower on nested queries |