Re: Request to share information regarding postgresql pg_xlog file. - Mailing list pgsql-general

On Sep 15, 2016, at 1:20 AM, Yogesh Sharma <Yogesh1.Sharma@nectechnologies.in> wrote:

Dear John and all,

 

>8.1 has been obsolete and unsupported for about 6 years now.    8.1.18 was released in 2009, the final 8.1.23 release was in 2010, after which it was >dropped.

Yes, we understood your point.

But we require some information related to this rpm.

 

>These errors suggest disk file corruption, this can occur from unreliable storage, undetected memory errors, and other such things.

How we can verify what is actual problem in system?

 

Also please share some information related to below.

we tried to stop the postgresql but it couldn’t stop and timout after 60 sec.

please confirm below message in postgre logs.

FATAL:  terminating connection due to administrator command

 

 

Regards,

Yogesh

 

From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of John R Pierce
Sent: Thursday, September 15, 2016 11:28 AM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Request to share information regarding postgresql pg_xlog file.

 

On 9/14/2016 10:09 PM, Yogesh Sharma wrote:

Thanks for your support and suggestion.

We are using below postgresql rpm.

postgresql-8.1.18-2.1

thats not the full RPM name, thats just the version.

8.1 has been obsolete and unsupported for about 6 years now.    8.1.18 was released in 2009, the final 8.1.23 release was in 2010, after which it was dropped.

current releases are 9.1 (soon to be obsoletted), 9.2, 9.3, 9.4, and 9.5, with 9.6 in release candidate state.

CONTEXT:  writing block 53 of relation 1663/16385/280951

ERROR:  could not open relation 1663/16385/280951: No such file or directory

These errors suggest disk file corruption, this can occur from unreliable storage, undetected memory errors, and other such things.

 

-- 

john r pierce, recycling bits in santa cruz