From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
---|---|
To: | <josh(at)agliodbs(dot)com> |
Cc: | <pgsql-hackers(at)postgresql(dot)org>, "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 20:28:36 |
Message-ID: | 1175200117.4386.616.camel@silverbirch.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-03-29 20:42:33 | Re: Modifying TOAST thresholds |
Previous Message | Joshua D. Drake | 2007-03-29 20:25:12 | Feature thought: idle in transaction timeout |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-03-29 22:06:33 | Re: DEALLOCATE ALL |
Previous Message | Bruce Momjian | 2007-03-29 20:24:53 | Re: [PATCH] add CLUSTER table USING index (take 2) |