Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] Full page writes improvement, code update

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Koichi Suzuki" <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [PATCHES] Full page writes improvement, code update
Date: 2007-03-29 18:45:27
Message-ID: 200703291145.28574.josh@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Simon,

> 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.

-- 
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Responses

pgsql-hackers by date

Next:From: Martijn van OosterhoutDate: 2007-03-29 18:54:05
Subject: Re: Server-side support of all encodings
Previous:From: Tom LaneDate: 2007-03-29 18:19:38
Subject: Re: Fixing insecure security definer functions

pgsql-patches by date

Next:From: Holger SchurigDate: 2007-03-29 19:27:19
Subject: Re: [PATCH] add CLUSTER table USING index (take 2)
Previous:From: Bruce MomjianDate: 2007-03-29 18:12:39
Subject: Re: tsearch_core patch for inclusion

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group