From: | Prajilal KP <prajilal(dot)kp(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Reg: PostgreSQL Server "base/data" recovery |
Date: | 2015-03-19 11:30:53 |
Message-ID: | CABsTp+DWs1ohRfqCZxj=rVErVj5gwt5=uE+6F+A0SNVjOnpMNw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> > 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:24 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com
> wrote:
> On Thu, Mar 19, 2015 at 8:12 PM, Prajilal KP <prajilal(dot)kp(at)gmail(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Igor Stassiy | 2015-03-19 11:54:59 | Get extensions directory programmatically in another Makefile |
Previous Message | Prajilal KP | 2015-03-19 11:30:51 | Re: Reg: PostgreSQL Server "base/data" recovery |