Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fCSOq-0001h1-2i for pgsql-hackers@arkaria.postgresql.org; Sat, 28 Apr 2018 16:08:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fCSOo-0001Dx-Po for pgsql-hackers@arkaria.postgresql.org; Sat, 28 Apr 2018 16:08:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fCSOn-0001Dn-Mg for pgsql-hackers@lists.postgresql.org; Sat, 28 Apr 2018 16:08:34 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fCSOk-0008Pd-2X for pgsql-hackers@postgresql.org; Sat, 28 Apr 2018 16:08:33 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 73501214F9; Sat, 28 Apr 2018 12:08:28 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sat, 28 Apr 2018 12:08:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=jRcdymp7lHJH1t9q5yXhL5izHl3dlNHEHkUooQv/V2s=; b=S0bSK8uX zlGWPpv6yJEX0/Ujnx4Zlq5gsQwwVVBXBtSpqEnoBH55l9FC5bF7J3yu6+/rZjP3 F4aV1PieJdhED4uJIHcmXuWTE57BzAaYrvlQZBuTO6HKM5pZZzY/9uHU0E+XXLwv eX44O8ICmdR2ZNGh5PJVHNYfTAnu1Ii7MAE47jlP9KdBA2ngc77hgcPb4vl5Sgg2 x2fNaLGZ/4PgKYtXTlRoTa6nc2pGJzfLkFcB1WGZMTr9wb9WqrIXbb3D1wZjXwem MvyDlxmKpF8giAhTWnZQyOXXUOyqzbdqN2rL2iXSiD7Zh1lekWyABo/sbOFuRNAC NBBYhrwUms7cqQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=jRcdymp7lHJH1t9q5yXhL5izHl3dl NHEHkUooQv/V2s=; b=nsc+1WcbiKwgt5wdqePEWO31yG+0IKxq9wYz/0Xtjy2Ni 1yb5hGJo9BCAO4gaKy2+pacO3UYzRx/v/BTLNMmMWybYHvNkQcVN37DNcV1V6eN3 iU4bIbjG22Nr6Yy/DOHmNfih1tP3LYyYgyPy3WZpWnfWQILdAQVnjw9gtU6oECpe AiN/uXPpoGiWnevk3qGpcoPE99zluxoHAyidRiy6jxLEZjy+XRsHCSqG+A4JbSCU P4cqFv9mCff4DslOhHRuXhhriltpAjQ4pHJNrbkwazjjHPEEpRTz46z7z5RqlrjV J3Z480HhbDy1W7svvz+UDMx8gVoS/xuhN0Ryqa14Q== X-ME-Sender: Received: from intern.anarazel.de (c-98-210-140-171.hsd1.ca.comcast.net [98.210.140.171]) by mail.messagingengine.com (Postfix) with ESMTPA id E3DA010256; Sat, 28 Apr 2018 12:08:27 -0400 (EDT) Date: Sat, 28 Apr 2018 09:08:26 -0700 From: Andres Freund To: Stephen Frost Cc: Bruce Momjian , Craig Ringer , PostgreSQL Hackers Subject: Re: Postgres, fsync, and OSs (specifically linux) Message-ID: <20180428160826.2e37ncq2cuh6rh34@alap3.anarazel.de> References: <20180427222842.in2e4mibx45zdth5@alap3.anarazel.de> <20180427230447.GA32605@momjian.us> <20180427231043.of7vhjmhx4qzexm7@alap3.anarazel.de> <20180427233830.GB32605@momjian.us> <20180427234332.wtkjvtkbpdl6mu6g@alap3.anarazel.de> <20180428151054.GR27724@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180428151054.GR27724@tamriel.snowman.net> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, On 2018-04-28 11:10:54 -0400, Stephen Frost wrote: > When we crash-restart, we also go through and clean things up some, no? > Seems like that gives us the potential to end up fixing things ourselves > and allowing the crash-restart to succeed. Sure, there's the potential for that. But it's quite possible to be missing a lot of free space over NFS (this really isn't much of an issue for local FS, at least not on linux) in a workload with rapidly expanding space usage. And even if you recover, you could just hit the issue again shortly afterwards. Greetings, Andres Freund