pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Craig Ringer <craig@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Abhijit Menon-Sen <ams@2ndquadrant.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Petr Jelinek <petr@2ndquadrant.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: 9.6 and fsync=off
Date: Mon, 02 May 2016 10:32:44 -0400
Message-ID: <20364.1462199564@sss.pgh.pa.us> (raw)
In-Reply-To: <CAMsr+YF4JUTP6pOsCBMd9QTw9uCAfS8tzfku1O=73wqTU7Y9Aw@mail.gmail.com>
References: <CAMsr+YGechDvrFj4xwoBWhJ7rW25Avqo+UqcyqbnS=LTFdGJ4g@mail.gmail.com>
	<20160427104307.GA4861@toroid.org>
	<CABUevExGL-FWNP0pyCH_9nY==i1ogP-v8XNXpQyDaEp7u4ypCA@mail.gmail.com>
	<57209AE7.9020906@2ndquadrant.com>
	<24748.1461764666@sss.pgh.pa.us>
	<CAMsr+YEy9zj2Nb_n8OFMAf2HpX-RVpb12sWYD2uakPy0Um9kag@mail.gmail.com>
	<CANP8+jLAph=Gk1hQy_+o8CvgxuHahZpgh7kqSy2LMq1+OsJS1A@mail.gmail.com>
	<20160428204423.sq2l675d2hamgr6m@alap3.anarazel.de>
	<20160429063514.GA630@toroid.org>
	<12906.1461937747@sss.pgh.pa.us>
	<CA+TgmobDk9pg3mvZLSwrnR3x022QmJyGPh4PsERx23iG9RcdVg@mail.gmail.com>
	<CAMsr+YF4JUTP6pOsCBMd9QTw9uCAfS8tzfku1O=73wqTU7Y9Aw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Craig Ringer <craig@2ndquadrant.com> writes:
> On 2 May 2016 at 22:07, Robert Haas <robertmhaas@gmail.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.

+1 for tracking this in pg_control (maybe even with a counter, not
just a flag).  I'm less convinced that we need to bleat on every
subsequent startup though --- that seems like just nagging.
Having the info available from pg_controldata seems sufficient for
forensics.

The timestamp ideas aren't bad either.

BTW, how would this work in a standby server?

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (21+ messages)  latest in thread

Message-ID: <20364.1462199564@sss.pgh.pa.us>
Permalink:  ../20364.1462199564@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/20364.1462199564@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, craig@2ndquadrant.com, robertmhaas@gmail.com, ams@2ndquadrant.com, andres@anarazel.de, simon@2ndquadrant.com, petr@2ndquadrant.com, magnus@hagander.net
  Subject: Re: 9.6 and fsync=off
  In-Reply-To: <20364.1462199564@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox