BUG #12812: invalid attribute number <number> for <table_name>

On Sat, Feb 28, 2015 at 3:29 PM, <ipnb87@gmail.com> wrote:

When selecting particular table or schema , views having that table shows
this error.
I also can't take backup this database or schema.

Could you send a test case that helps to reproduce the problem you are
seeing and the error message you are seeing? I am afraid that with so
little information there is not much we can do..
--
Michael

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Hi Michal,

It is record tables. Thousands of record inserted in that tables per day.
Till yesterday noon there is no problem. When I take a backup at yesterday
night the I found 0 kb dump file. Then I taken backup all three schema
separately.
Problem found in "AD" schema.

Then I try to select that particular table, I got following error.
(Screenshot attached). Re indexing for that table also failed due to that
error.

ERROR: invalid attribute number 24932 for transaction_set
LINE 1: SELECT * FROM AD_GSS_DMS_P.TRANSACTION_SET
^
********** Error **********

ERROR: invalid attribute number 24932 for transaction_set
SQL state: XX000
Character: 15

[image: Inline images 2]

*​--*
*​**Regards,*
*Iyappan,*
*Global Software Solutions (TVL) Pvt. Ltd.,*
*+91 97152 30226*

On 28 February 2015 at 12:33, Michael Paquier <michael.paquier@gmail.com>
wrote:

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.

--
john r pierce 37N 122W
somewhere on the middle of the left coast

John R Pierce <pierce@hogranch.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

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Thanks John,
I also try to re index for pg_attribute and that particular table, but that
is also failed. We will check the reason for Postgres itself crash. I hope
upcoming version may address this problem.
On 28-Feb-2015 9:28 pm, "Tom Lane" <tgl@sss.pgh.pa.us> wrote: