Re: tackling full page writes

From: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: tackling full page writes
Date: 2011-05-27 18:57:04
Message-ID: 20110527185704.GA2583@cnx.rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 25, 2011 at 01:29:05PM -0400, Robert Haas wrote:
> On Wed, May 25, 2011 at 1:06 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> > On 05/24/2011 04:34 PM, Robert Haas wrote:
>
> > I've been looking into a similar refactoring of the names here, where we
> > bundle all of these speed over safety things (fsync, full_page_writes, etc.)
> > into one control so they're easier to turn off at once.  Not sure if it
> > should be named "web_scale" or "do_you_feel_lucky_punk".
>
> Actually, I suggested that same idea to you, or someone, a while back,
> only I was serious. crash_safety=off. I never got around to fleshing
> out the details, though.

clearly:

crash_safety=running_with_scissors

--
Ross Reedstrom, Ph.D. reedstrm(at)rice(dot)edu
Systems Engineer & Admin, Research Scientist phone: 713-348-6166
Connexions http://cnx.org fax: 713-348-3665
Rice University MS-375, Houston, TX 77005
GPG Key fingerprint = F023 82C8 9B0E 2CC6 0D8E F888 D3AE 810E 88F0 BEDE

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-05-27 19:02:53 Re: tackling full page writes
Previous Message Robert Haas 2011-05-27 18:39:26 Re: How can I check the treatment of bug fixes?