| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 9.6 and fsync=off |
| Date: | 2016-04-28 18:53:50 |
| Message-ID: | CAM-w4HOJmMzR04OOHh6mk-rPfcbgGyVKfmgPWXsOJnmR_0sC7Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 27, 2016 at 10:58 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> Now, we can't rename fsync to disable_crash_safety=on or
> corrupt_my_database=on. But the comment needs changing.
Fwiw we've done similar things in the past. We can provide
backwards-compatibility support for "fsync" but make the setting
appear as "crash_safety" or whatever in pg_settings and in the default
postgres.conf. The only downside is that tools or scripts that
retrieve all the settings might break or miss that setting.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2016-04-28 19:32:37 | Re: 9.6 and fsync=off |
| Previous Message | David Fetter | 2016-04-28 17:56:21 | Re: Add jsonb_compact(...) for whitespace-free jsonb to text |