On Wed, Apr 27, 2016 at 10:58 AM, Craig Ringer <cr...@2ndquadrant.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
