From: Andres Freund <andres@anarazel.de>
To: Stephen Frost <sfrost@snowman.net>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Craig Ringer <craig@2ndquadrant.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Postgres, fsync, and OSs (specifically linux)
Date: Sat, 28 Apr 2018 09:08:26 -0700
Message-ID: <20180428160826.2e37ncq2cuh6rh34@alap3.anarazel.de> (raw)
In-Reply-To: <20180428151054.GR27724@tamriel.snowman.net>
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>
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
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: andres@anarazel.de, sfrost@snowman.net, bruce@momjian.us, craig@2ndquadrant.com
Subject: Re: Postgres, fsync, and OSs (specifically linux)
In-Reply-To: <20180428160826.2e37ncq2cuh6rh34@alap3.anarazel.de>
* 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