Need help on postgres related to insertion of a tuple. - Mailing list pgsql-general

From M Tarkeshwar Rao
Subject Need help on postgres related to insertion of a tuple.
Date
Msg-id 1C16813DAFF3E44B939586605D40E9F0240E6B4A@ESESSMB107.ericsson.se
Whole thread Raw
Responses Re: Need help on postgres related to insertion of a tuple.  (Michael Paquier <michael.paquier@gmail.com>)
Re: Need help on postgres related to insertion of a tuple.  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general

Hi all,

 

We have a table name auditTrailLogEntry where we were not able to able to insert in auditTrailLogEntry table.

 

we have reindex the table and insertion issue has been resolved .

 

we executed following command:


Audit tail insertion issue.

INSERT INTO auditTrailLogEntry (event, inNodeID, inNodeName, sourceID, inTime, outNodeID, outNodeName, destinationID, outTime, bytes, cdrs, tableIndex, noOfSubfilesInFile, recordSequenceNumberList ) VALUES (68, NULL, NULL, E'proc_PGWDiskCollectorGroup1_0_1434566783_1027213', E'2015-06-17 11:46:32.224', E'3434', E'PGW ACC MVNE2 Raw', E'DEPCF003.2015-06-1711-41-06.8493.BGWP21S5M2P1.000328122', E'2015-06-17 11:46:33.790', 39193, 78, 952


Got following error messages

ERROR: unexpected data beyond EOF in block 260 of relation pg_tblspc/16388/PG_9.1_201105231/16384/16418
HINT: This has been seen to occur with buggy kernels; consider updating your system.
Failed to transfer a row to the database table auditTrailLogEntry.
The SQL statement to execute was: INSERT INTO auditTrailLogEntry (event, inNodeID, inNodeName, sourceID, inTime, outNodeID, outNodeName, destinationID, outTime, bytes, cdrs, tableIndex, noOfSubfilesInFile, recordSequenceNumberList ) VALUES (68, NULL, NULL, E'proc_PGWDiskCollectorGroup1_0_1434566783_1027213', E'2015-06-17 11:46:32.224', E'3434', E'PGW ACC MVNE2 Raw', E'DEPCF003.2015-06-1711-41-06.8493.BGWP21S5M2P1.000328122', E'2015-06-17 11:46:33.790', 39193, 78, 952

 

Can you please suggest following:

----------------------------------------------

a. How can we prevent "This has been seen to occur with buggy kernels; consider updating your system" alarm ?
b. how can resolve "This has been seen to occur with buggy kernels; consider updating your system" alarm ?

 

Regards

Tarkeshwar

pgsql-general by date:

Previous
From: Ken Tanzer
Date:
Subject: Re: EXCLUDE, Gist and integers
Next
From: Mitu Verma
Date:
Subject: Re: unexpected data beyond EOF in block 260 of relation pg_tblspc