On 4/28/2016 1:33 AM, Yogesh Sharma wrote:
>did you get that 'no such file or directory' error before or after you reset the transaction logs ?
The error message is coming before.
that means your file system lost files. there's a number of ways that can happen, mostly revolving around file systems with unreliable caching combined with a power failure, or physical hardware data corruption can do it too. mucking about in the postgres data file system can do it, too, of course. do you have backups from before this occurred ?
>messing with the write-ahead logs is very dangerous. that blog is talking about postgres 8.4, based on his paths. is that what you're running?
We are running postgres 8.3.
thats a completely obsolete version, 8.3.23 was last updated in early 2013.
current supported versions are 9.1, 9.2, 9.3, 9.4, and 9.5
current releases: 9.1.21, 9.2.16, 9.3.12, 9.4.7, and 9.5.2
--
john r pierce, recycling bits in santa cruz
