| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it> |
| Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [SPAM] Re: [SPAM] Re: WAL directory size calculation |
| Date: | 2016-08-03 12:12:24 |
| Message-ID: | CAB7nPqSJ-d+hHn2D2RnOdXfwuYPmJbo80QZ4Z9D6fRv7UicO=A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Aug 3, 2016 at 8:07 PM, Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it> wrote:
> Should I keep fsync off? I'd think it would be better leaving it on, right?
From the docs: https://www.postgresql.org/docs/9.6/static/runtime-config-wal.html#RUNTIME-CONFIG-WAL-SETTINGS
While turning off fsync is often a performance benefit, this can
result in unrecoverable data corruption in the event of a power
failure or system crash. Thus it is only advisable to turn off fsync
if you can easily recreate your entire database from external data.
So if you care about your data, that's to set in any case to on, as is
full_page_writes.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Moreno Andreo | 2016-08-03 12:19:06 | Re: [SPAM] Re: [SPAM] Re: [SPAM] Re: WAL directory size calculation |
| Previous Message | Andrea Martino | 2016-08-03 11:55:54 | Per-statement trigger in Foreign tables in Posgregsql 9.4 (through Foreign-data wrapper) |