From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org, IPN Bala GSS TVL <ipnb87(at)gmail(dot)com> |
Subject: | Re: BUG #12812: invalid attribute number <number> for <table_name> |
Date: | 2015-02-28 15:58:15 |
Message-ID: | 27738.1425139095@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
John R Pierce <pierce(at)hogranch(dot)com> writes:
> On 2/28/2015 1:50 AM, IPN Bala GSS TVL wrote:
>> ERROR: invalid attribute number 24932 for transaction_set
>> LINE 1: SELECT * FROM AD_GSS_DMS_P.TRANSACTION_SET
> that looks like data corruption may have occurred.
Yeah :-(. The only occurrence of that message text in 9.3 is in
RelationBuildTupleDesc, and it's saying it found a row in pg_attribute
with that attnum and the mentioned table's attrelid. The attnum is
obviously bogus for any row in pg_attribute, ergo something has corrupted
data in pg_attribute. It's unlikely that only one row has been corrupted,
too :-(
Depending on how valuable that database is, you might want to go back
to your last backups, or you might want to seek professional help
--- there are assorted consulting companies that specialize in dealing
with data-corruption situations.
In any case you should try to identify the cause of the problem.
It's more than likely a hardware or OS problem --- there are few
known reasons for Postgres itself to cause this sort of failure.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | IPN Bala GSS TVL | 2015-02-28 16:13:09 | Re: BUG #12812: invalid attribute number <number> for <table_name> |
Previous Message | John R Pierce | 2015-02-28 09:58:56 | Re: BUG #12812: invalid attribute number <number> for <table_name> |