Dear All,
Could you please update your suggestion on below mail
Regards,
Yogesh
From: Yogesh Sharma
Sent: Friday, April 29, 2016 3:57 PM
To: John R Pierce; pgsql-general@postgresql.org
Subject: RE: [GENERAL] Issue during postgresql startup
Dear All,
I am sharing my further observation regarding the system behavior.
The errors related to this missing table file started coming from 2016-04-24
20:37:11 till the end when pg_xlog filled up the disk space and postgres
crashed eventually.
postgresql_log.Sun.gz:<%2016-04-24 20:37:11 GMT> ERROR: could not open
relation 1663/16385/1299988: No such file or directory
PostgreSQL:PANIC: could not write to file "pg_xlog/xlogtemp.21498": No space
left on device server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
Furthermore, as a periodic maintenance REINDEXING of table executed at
2016-04-24 20:33:05, Although table file is recreated at index reconstruction,
for some reason, the recreated table file 1299988 got deleted, and probably led
to this issue.
There is a difference of roughly 4 minutes between the REINDEXING and the point
where this error start coming. I am trying to find out if there is any sort of
relation between postgres and table file deletion (Probably some sort of bug in
postgres ?).
As an experiment I tried to create a dummy file “1663/16385/1299988” using dd
command and triggered postgres start but postgres delete the dummy file
automatically. Due to this sort of behavior I am suspecting that the actual
file created after REINDEX might be having some sort of corruption and postgres
deleted that file automatically.
I’ll appreciate any kind of opinion on my understanding.
Thanks,
Yogesh Sharma
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: Thursday, April 28, 2016 2:51 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Issue during postgresql startup
On 4/28/2016 1:54 AM, Yogesh Sharma wrote:
>do you have backups from before this occurred ?
No, there is no backup available for the same.
oops.
it is possible some of your tables can be recovered by someone highly
experienced in postgres data recovery. such people work for the various
postgres consultancies, like 2nd Quadrant, and so forth. I sure don't know
the intricacies of doing this. 8.3 is a really old obsolete version, too...
its life cycle ran from Feb. 2008 to Feb 2013.
--
john r pierce, recycling bits in santa cruz
DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and
intended
for the named recipient(s) only.
It shall not attach any liability on the originator or NEC or its
affiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the
opinions of NEC or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of
this message without the prior written consent of the author of this e-mail is
strictly prohibited. If you have
received this email in error please delete it and notify the sender
immediately. .
-----------------------------------------------------------------------------------------------------------------------
