> 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.
PostgreSQL @ Sun
In response to
pgsql-hackers by date
|Next:||From: Martijn van Oosterhout||Date: 2007-03-29 18:54:05|
|Subject: Re: Server-side support of all encodings|
|Previous:||From: Tom Lane||Date: 2007-03-29 18:19:38|
|Subject: Re: Fixing insecure security definer functions |
pgsql-patches by date
|Next:||From: Holger Schurig||Date: 2007-03-29 19:27:19|
|Subject: Re: [PATCH] add CLUSTER table USING index (take 2)|
|Previous:||From: Bruce Momjian||Date: 2007-03-29 18:12:39|
|Subject: Re: tsearch_core patch for inclusion|