Re: unexpected data beyond EOF in block 260 of relation pg_tblspc

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Mitu Verma <mitu(dot)verma(at)ericsson(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: unexpected data beyond EOF in block 260 of relation pg_tblspc
Date: 2015-07-06 12:54:39
Message-ID: 559A7A8F.20105@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 07/05/2015 10:15 PM, Mitu Verma wrote:
> Hi,
> Below alarm was raised at the system where postgres database was used..
> -----------------------------------------------------------------------------------------------------------
> BGWPOL22-00:/var/opt/mediation/MMStorage6/Server8/CXC1734739_R8J/storage/logging/ACTIVE#
> cat AA::80165730a!
> 1434566795-Server8eBGWPOL22-00!! iThere is a problem with the system
> environment (memory, disk, etc).
> Failed to store log information in the database in AUDIT
> 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.
> -----------------------------------------------------------------------------------------------------------
> Entry into the table Is also getting failed due to this.
> If this is an issue with the postgres DB or some problem with the kernel?
> Please help by giving some pointers and in what circumstances this issue
> can occur?

It would be helpful to know more information:

1) OS and version?

2) Postgres version?

3) Kernel version?

4) Storage type? In particular what is the tablespace stored on?

> Regards
> Mit

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jan de Visser 2015-07-06 13:41:27 Re: [pg_hba.conf] publish own Python application using PostgreSQL
Previous Message Rob Sargent 2015-07-06 12:47:56 Re: Error prone compilation of stored procedure