| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 9.6 and fsync=off |
| Date: | 2016-05-02 14:27:08 |
| Message-ID: | CAMsr+YF4JUTP6pOsCBMd9QTw9uCAfS8tzfku1O=73wqTU7Y9Aw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2 May 2016 at 22:07, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> I also think that it would be a swell idea to detect whether a system
> has ever crashed with fsync=off, and do something about that, like
> maybe bleat on every subsequent startup for the lifetime of the
> cluster.
Yes. Very, very yes.
That would've made my life considerably easier on a few occasions now.
It shouldn't take much more than a new pg_control field and a test during
recovery.
Should TODO this, but since that's sometimes where ideas go to die, I'm
going to see if I can hack this out soon as well.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | david | 2016-05-02 14:32:04 | Re: About subxact and xact nesting level... |
| Previous Message | Tom Lane | 2016-05-02 14:22:56 | Re: Refactor pg_dump as a library? |