Re: Redesigning checkpoint_segments

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Daniel Farina <daniel(at)heroku(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Redesigning checkpoint_segments
Date: 2013-06-06 05:54:05
Message-ID: CAM3SWZTAdXZv9GAk_fi=73kymUDs=C865hL6q_1j4hSa4XafDg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 5, 2013 at 10:27 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> I just wonder if we are looking in the right place (outside of some obvious
> badness like the PANIC running out of disk space).

So you don't think we should PANIC on running out of disk space? If
you don't think we should do that, and you don't think that WAL
writing should be throttled, what's the alternative?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Farina 2013-06-06 06:04:08 Re: Redesigning checkpoint_segments
Previous Message Joshua D. Drake 2013-06-06 05:27:26 Re: Redesigning checkpoint_segments