<p dir="ltr"><br /> On Sep 3, 2013 6:23 PM, "Josh Berkus" <<a
href="mailto:josh@agliodbs.com">josh@agliodbs.com</a>>wrote:<br /> ><br /> > Peter,<br /> ><br /> ><br
/>> > I wonder, is anyone really running in production with full_page_writes<br /> > > off?<br /> ><br
/>> We're doing so with clients on Joyent (ZFS). And also for "ephemeral"<br /> > postgres instances -- ones
wherewe've also turned off fsync.<br /> ><br /> > It's also quite reasonable to assume that future filesystems
willalso<br /> > be able to make better torn page guarantees.<br /> ><br /> > So it should remain a setting.
Isee no reason why it should be a<br /> > SIGHUP setting, though, if there's any code maintenance required to<br />
>support it -- frankly, I only change this setting at first system<br /> > deployment.<br /> ><p
dir="ltr">Thismatches my experience as well - people certainly use it, but don't change it during runtime.<p
dir="ltr">Nothaving looked at the code, but doesn't pg_start_backup use at least parts of the same code path? That one
willdefinitely still be able to modify it at runtime.... <p dir="ltr">/Magnus