Thread: FATAL 2: PageIndexTupleDelete
salt=# vacuum full;
FATAL 2: PageIndexTupleDelete: corrupted page pointers: lower = 12289, upper =
1, special = 60672
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.
Why do I have this error message and how can I fix it?
cristi wrote: > salt=# vacuum full; > > FATAL 2: PageIndexTupleDelete: corrupted page pointers: lower = 12289, > upper = > > 1, special = 60672 > > server closed the connection unexpectedly > > This probably means the server terminated abnormally > > before or while processing the request. > > The connection to the server was lost. Attempting reset: Succeeded. > > > > Why do I have this error message and how can I fix it? Wich version are you running, and what about give us informations on your platform ? Regards Gaetano Mendola
"cristi" <cristi@dmhi.ct.ro> writes:
> FATAL 2: PageIndexTupleDelete: corrupted page pointers: lower =3D 12289, up=
> per =3D
> 1, special =3D 60672
> Why do I have this error message and how can I fix it?
This is a data-corruption problem. Have you had any system crashes or
other odd behavior lately?
As far as recovering, you can probably fix the broken index with
REINDEX, if the corruption doesn't extend further than the index that's
being complained of. Otherwise you might have to resort to a dump and
reload.
You should also think about updating your Postgres installation. You
didn't say what version you're running (naughty naughty, that's required
info in any trouble report) but I can tell from the spelling of the
error message that it's not a current release.
regards, tom lane
Yes, you right! I used pg_dump command and now is working. Thank you very much! PS. I have version 7.2.2 on RH 8.0 > > FATAL 2: PageIndexTupleDelete: corrupted page pointers: lower =3D 12289, up= > > per =3D > > 1, special =3D 60672 > > > Why do I have this error message and how can I fix it? > > This is a data-corruption problem. Have you had any system crashes or > other odd behavior lately? > > As far as recovering, you can probably fix the broken index with > REINDEX, if the corruption doesn't extend further than the index that's > being complained of. Otherwise you might have to resort to a dump and > reload. > > You should also think about updating your Postgres installation. You > didn't say what version you're running (naughty naughty, that's required > info in any trouble report) but I can tell from the spelling of the > error message that it's not a current release. > > regards, tom lane >