| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Prajilal KP <prajilal(dot)kp(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:24:01 |
| Message-ID: | CAB7nPqQEfA5Jw+BHswOob-8UuNixixAYxmkt2hu0sjHj=N9fmA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 | Prajilal KP | 2015-03-19 11:30:51 | Re: Reg: PostgreSQL Server "base/data" recovery |
| Previous Message | Prajilal KP | 2015-03-19 11:12:27 | Re: Reg: PostgreSQL Server "base/data" recovery |