Thread: Need help on postgres related to insertion of a tuple.

On Thu, Jul 16, 2015 at 5:18 PM, M Tarkeshwar Rao
<m.tarkeshwar.rao@ericsson.com> wrote:
> 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 ?

This defense has been added by this commit some time ago:
commit: ffae5cc5a6024b4e25ec920ed5c4dfac649605f8
author: Tom Lane <tgl@sss.pgh.pa.us>
date: Mon, 25 Sep 2006 22:01:10 +0000
Add a check to prevent overwriting valid data if smgrnblocks() gives a
wrong answer, as has been seen to occur with a buggy Linux kernel.  Not
really our bug, but it's a simple test in a seldom-used control path,
so might as well have a defense.

And if you look at the comment on top of this error message this code
is a protection against lseek(SEEK_END) that may be buggy on some old
kernels. Hence the answer to both questions is in the error message:
upgrade your system to a newer kernel or migrate to a newer server.
--
Michael

On 07/16/2015 01:18 AM, M Tarkeshwar Rao wrote:
> 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


Just to be clear this is a duplicate of this thread?:

http://www.postgresql.org/message-id/84BC7AB0D621A74893EC9C9E151293B0226D8ED1@ESESSMB207.ericsson.se

>
> *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
>


--
Adrian Klaver
adrian.klaver@aklaver.com