Re: Remove fsync ON/OFF as a visible option?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove fsync ON/OFF as a visible option?
Date: 2015-04-02 18:27:56
Message-ID: CA+Tgmoa71EV9CoY6udhdQaP=SjtAEowYQ6onFsjeVB79y8ztuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 25, 2015 at 3:45 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> I see 3 settings that allow people to accidentally shoot themselves in the
> foot; fsync, wal_sync_method and full_page_writes.

Those aren't even the top three in my experience, let alone the only three.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-04-02 18:30:30 Re: Fix pgbench --progress report under (very) low rate
Previous Message Robert Haas 2015-04-02 18:24:13 Re: [HACKERS] GSoC 2015 proposal: Improve the performance of “ALTER TABLE .. SET LOGGED / UNLOGGED” statement