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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: M Tarkeshwar Rao <m(dot)tarkeshwar(dot)rao(at)ericsson(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Need help on postgres related to insertion of a tuple.
Date: 2015-07-16 13:09:39
Message-ID: CAB7nPqSSokz22k6y+zGw61Jz8u0rzBxRGCyeCNB8m1+ez2t4Pw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jul 16, 2015 at 5:18 PM, M Tarkeshwar Rao
<m(dot)tarkeshwar(dot)rao(at)ericsson(dot)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(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2015-07-16 13:30:30 Re: Need help on postgres related to insertion of a tuple.
Previous Message Ronald Peterson 2015-07-16 12:14:47 Re: utf8 encoding problem with plperlu