pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: josh@agliodbs.com
Cc: pgsql-hackers@postgresql.org
Cc: Koichi Suzuki <suzuki.koichi@oss.ntt.co.jp>
Cc: pgsql-patches@postgresql.org
Subject: Re: [PATCHES] Full page writes improvement, code update
Date: Thu, 29 Mar 2007 21:28:36 +0100
Message-ID: <1175200117.4386.616.camel@silverbirch.site> (raw)
In-Reply-To: <200703291145.28574.josh@agliodbs.com>
References: <460886E8.6040907@oss.ntt.co.jp>
	<4609CAC3.7060008@oss.ntt.co.jp>
	<1175072848.4386.323.camel@silverbirch.site>
	<200703291145.28574.josh@agliodbs.com>

On Thu, 2007-03-29 at 11:45 -0700, Josh Berkus wrote:

> > OK, different question:
> > Why would anyone ever set full_page_compress = off?
> 
> The only reason I can see is if compression costs us CPU but gains RAM & 
> I/O.  I can think of a lot of applications ... benchmarks included ... 
> which are CPU-bound but not RAM or I/O bound.  For those applications, 
> compression is a bad tradeoff.
> 
> If, however, CPU used for compression is made up elsewhere through smaller 
> file processing, then I'd agree that we don't need a switch.

Koichi-san has explained things for me now.

I misunderstood what the parameter did and reading your post, ISTM you
have as well. I do hope Koichi-san will alter the name to allow
everybody to understand what it does.

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com





view thread (64+ messages)  latest in thread

Message-ID: <1175200117.4386.616.camel@silverbirch.site>
Permalink:  ../1175200117.4386.616.camel@silverbirch.site/
Also on:    postgresql.org/message-id/1175200117.4386.616.camel@silverbirch.site

 · 

reply

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: simon@2ndquadrant.com, josh@agliodbs.com, suzuki.koichi@oss.ntt.co.jp, pgsql-patches@postgresql.org
  Subject: Re: [PATCHES] Full page writes improvement, code update
  In-Reply-To: <1175200117.4386.616.camel@silverbirch.site>

* 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