Re: Redesigning checkpoint_segments

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Redesigning checkpoint_segments
Date: 2013-07-08 18:38:29
Message-ID: 51DB0725.3070901@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07/03/2013 11:28 AM, Peter Eisentraut wrote:
> On 6/6/13 4:09 PM, Heikki Linnakangas wrote:
> I don't understand what this patch, by itself, will accomplish in terms
> of the originally stated goals of making checkpoint_segments easier to
> tune, and controlling disk space used. To some degree, it makes both of
> these things worse, because you can no longer use checkpoint_segments to
> control the disk space. Instead, it is replaced by magic.
>
> What sort of behavior are you expecting to come out of this? In testing,
> I didn't see much of a difference. Although I'd expect that this would
> actually preallocate fewer segments than the old formula.

Since I haven't seen a reply to Peter's comments from Heikki, I'm
marking this patch "returned with feedback". I know, it's a very busy
CF, and I'm sure that you just couldn't get back to this one. We'll
address it in September?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2013-07-08 18:48:53 Re: Add visibility map information to pg_freespace.
Previous Message Josh Berkus 2013-07-08 18:34:33 Re: preserving forensic information when we freeze