> > I see, As there are many reasons exists for the data corruption i couldn't > > figure out it exactly. > > Unfortunately there is no backup for this system and is not possible to > > restore from the backup. > > Well, then, lost data is lost.
Oh.. My bad ... > > > I have been using the NFS storage since 2013 and didn't experience this > > issue before, now i am afraid. > > We haven't set to run the fysnc() in our environment. > > > > If i set "fysnc to on" now, did it make any impact to current flow? > > Having fsync = off in postgresql.conf is a perfect method to corrupt > your data, you should really not set it to off. Okay, I will take action immediately to set the fync=on. I hope it with save me for a period. I will consider upgrading to a later version at the earliest.. Thank you very much Prajilal On Thu, Mar 19, 2015 at 8:12 PM, Prajilal KP <prajilal...@gmail.com> wrote: > I see, As there are many reasons exists for the data corruption i couldn't > figure out it exactly. > Unfortunately there is no backup for this system and is not possible to > restore from the backup. Well, then, lost data is lost. > I have been using the NFS storage since 2013 and didn't experience this > issue before, now i am afraid. > We haven't set to run the fysnc() in our environment. > > If i set "fysnc to on" now, did it make any impact to current flow? Having fsync = off in postgresql.conf is a perfect method to corrupt your data, you should really not set it to off. -- Michael
