Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1avNAZ-0004uW-JQ for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Apr 2016 10:58:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1avNAZ-0001c7-54 for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Apr 2016 10:58:11 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1avN9D-0008Mp-TN for pgsql-hackers@postgresql.org; Wed, 27 Apr 2016 10:56:48 +0000 Received: from mail-wm0-x22b.google.com ([2a00:1450:400c:c09::22b]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1avN9A-0006e6-F0 for pgsql-hackers@postgresql.org; Wed, 27 Apr 2016 10:56:46 +0000 Received: by mail-wm0-x22b.google.com with SMTP id g17so7449032wme.0 for ; Wed, 27 Apr 2016 03:56:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=vWWIwRIgFoa+UTFUwVSZYRhz4bGhk0EsM40d2w+6DKQ=; b=sjbopAtmIWPcunZTGK4/JiWz8lGJ0tR84bizM1ZKQQgiWkaHQNDDjVTugVmy3kG4ua b2weFcAwDrj+/YQVI7AunGJgNwg5fFSvB6MUFQeLzTs5vZRLm+ZsqCTnWI81t8x7NU9I bHtwXuXgHkmaNlMQYLYfaF1HJCC/cfE76Nxj5np9K0YasfSSJWW9W//R7arGbeI1lwpl suWjyif/VQ7DJ65ajqCUjwC6hZ0jjT/alnOWrIsBKUrGVR0vW4tH13bd2z3ov3fawW9W ThwFukPGDbCJTtFp/onyihfxGyFnBwKgPVCgBTP8W7sYaX0XqeyL1zFHXvqBKN696a/4 6v7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=vWWIwRIgFoa+UTFUwVSZYRhz4bGhk0EsM40d2w+6DKQ=; b=m+vexsha4X5zuEUL5eN6JsLANF37jcexPrZcXKx7MjoLmSyrsgiERGfKH0nXyU4ia+ cmIgmUW0KsmYRfKnaa5fIVk2hWKUOAkrwFuQoJaOrhGFPlBZfc+bTubxM8uAntqUQq7I WZRO8hW0dPhh6fiXodxuMD1akVu//eqmw1+gCJBcZ/QBptMyYSq58PpMujOlodXyXjdY vIj55QeDIrhmh91UNwRzQTq0jg/iVszrx4SsEvCi0U1qsbYKr5v6VlkorlMv6w6hfBZ/ bIVCsavve5wOnAi8j0TySvZSSxDf06z38mhNLB3ArOtLNtbjp+/2cyndxk97UII6UElJ T62w== X-Gm-Message-State: AOPr4FV8NqyVmyQL64KsMXvV07BnxncOFeB+tRMQvh7RF0TekchabBwRksUIy+yQ1gdmBDBNv+8ZVMM3UIAsIUfhO16rO4/AfajW7R/bj/4azEG+QR/YKgkwzxR01r5JTphbN2BgJVGLq7F/N6ZJm8WrDc5Xt0SmXgmchnoYtULHlUZKGcBpcEK4hL35I2SJQA== X-Received: by 10.28.105.200 with SMTP id z69mr9075300wmh.78.1461754601700; Wed, 27 Apr 2016 03:56:41 -0700 (PDT) Received: from [192.168.0.103] (150.123.broadband11.iol.cz. [90.178.123.150]) by smtp.gmail.com with ESMTPSA id gt7sm3450270wjc.1.2016.04.27.03.56.40 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Apr 2016 03:56:40 -0700 (PDT) Subject: Re: 9.6 and fsync=off To: Magnus Hagander , Abhijit Menon-Sen References: <20160427104307.GA4861@toroid.org> Cc: Craig Ringer , PostgreSQL-development From: Petr Jelinek Message-ID: <57209AE7.9020906@2ndquadrant.com> Date: Wed, 27 Apr 2016 12:56:39 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 27/04/16 12:53, Magnus Hagander wrote: > > > On Wed, Apr 27, 2016 at 12:43 PM, Abhijit Menon-Sen > wrote: > > At 2016-04-27 17:58:08 +0800, craig@2ndquadrant.com > wrote: > > > > #fsync = on # turns forced synchronization on or off > > I suggest: # provide crash safety by > flushing disk writes > # (Disabling this can > lead to unrecoverable data > # loss if the system > crashes.) > > > +1 for the change. I suggest shortening it to just "disabling this can > lead to unrecoverable data corruption" (I think corruption is better > than loss, mainly because too many people equate loss with "i may loose > my last 10 updates, and I'm fine with that). > +1 (Abhijit's wording with data loss changed to data corruption) -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers