From: | Joao Ferreira gmail <joao(dot)miguel(dot)c(dot)ferreira(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | failed to re-find parent key in "..." |
Date: | 2008-08-18 10:09:12 |
Message-ID: | 1219054152.6456.30.camel@jmf-ubuntu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello all,
a few days ago I bumped into this:
---------------------------------------------
# vacuumdb -f -z -a
vacuumdb: vacuuming database "postgres"
VACUUM
vacuumdb: vacuuming database "rtdata"
vacuumdb: vacuuming of database "rtdata" failed: ERROR: failed to
re-find parent key in "timeslots_strs_var_ts_key"
---------------------------------------------
We are using postgres 8.1.4 and I realise this has been fixed in 8.1.6
but...
...before updating all our servers I need to have an idea of the extent
of the impact of this error.
It seems to me that this error may cause the VACUUM, AUTOVACUUM and
VACUUM FULL operations to fail partially or totally. Am I correct ? Or
does this only have impact on VACUUM FULL ?
We run many servers with a database application very heavily updated. In
this scenario do I tell my boss that "updating postgres would be nice"
or that we "we _must_ update postgres" ?
What risks are we facing if we choose not to update postgresql ?
thanks a lot for your advice.
joao
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Tom | 2008-08-18 10:09:23 | Re: pg_restore fails on Windows |
Previous Message | Ow Mun Heng | 2008-08-18 09:43:45 | Re: What's size of your PostgreSQL Database? |