From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, "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-03-22 13:45:52 |
Message-ID: | 20150322134552.GA3241@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2015-03-21 13:53:47 -0700, Josh Berkus wrote:
> Coincidentally, I am just at this moment performance testing "running
> with scissors mode" for PostgreSQL on AWS. When intentional, this mode
> is useful for spinning up lots of read-only replicas which are intended
> mainly as cache support, something I've done at various dot-coms.
Which is where fsync=off barely has any effect?
> So, -1 on removing the setting; it is useful to some users.
Agreed on that.
> Further, full_page_writes=off is supposedly safe on any copy-on-write
> filesystem, such as ZFS.
FWIW, I think that's a myth. One I heard various versions of by now. As
long as the OSs page size (4kb nearly everywhere) is different from
postgres' (8kb) you can have torn pages. Even if individual filesystem
page writes are atomic.
> The proposal that we make certain settings "only available via ALTER
> SYSTEM" also doesn't make sense; ALTER SYSTEM isn't capable of writing
> any settings which aren't available in postgresql.conf.
+1. I think it's a pretty absurd sugestion.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2015-03-22 14:30:36 | Re: Order of enforcement of CHECK constraints? |
Previous Message | Andreas Karlsson | 2015-03-22 12:59:22 | Re: Using 128-bit integers for sum, avg and statistics aggregates |