| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | geva <geva(at)regard(dot)co(dot)il> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: vacuum bug |
| Date: | 2002-10-23 13:19:50 |
| Message-ID: | 20021023061855.W3876-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, 20 Oct 2002, geva wrote:
>
> i'm encountering an recurring problem in which running vacuum on a
> relatively large
> database ( >30000 rows) causes the database to corrupt rather badly. all
> subsequent calls to vacuum does not return, and the only solution is to
> pg_dump the database, drop all or some of the tables, and recover the
> database using \i or psql -e.
>
> i am working with version 7.0 .
>
> is it a known bug ? was it solved on later versions? is there a
> workaround?
It's hard to say, there have been bugs related to vacuum fixed in later
versions. 7.0 is pretty old at this point (between 2 and 3 revisions back
since 7.3 is in beta), you'd probably be best off upgrading if possible.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2002-10-23 13:24:06 | Re: Error in chkpass.c (contrib area) with suggestion |
| Previous Message | Stephan Szabo | 2002-10-23 13:16:08 | Re: now() gives the time of the last commit, not the time it |