Re: [REVIEW] Re: Compression of full-page-writes - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [REVIEW] Re: Compression of full-page-writes
Date
Msg-id CA+TgmoarY=L2GZBbJXmdzSNdozahz12qaf7213htiqurEA3Faw@mail.gmail.com
Whole thread Raw
In response to Re: [REVIEW] Re: Compression of full-page-writes  (Rahila Syed <rahilasyed.90@gmail.com>)
Responses Re: [REVIEW] Re: Compression of full-page-writes  (Rahila Syed <rahilasyed.90@gmail.com>)
Re: [REVIEW] Re: Compression of full-page-writes  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Thu, Dec 4, 2014 at 5:36 AM, Rahila Syed <rahilasyed.90@gmail.com> wrote:
> The only scenario in which a user would not want to compress forcibly
> written pages is when CPU utilization is high.

Or if they think the code to compress full pages is buggy.

> But according to measurements
> done earlier the CPU utilization  of compress=’on’ and ‘off’ are not
> significantly different.

If that's really true, we could consider having no configuration any
time, and just compressing always.  But I'm skeptical that it's
actually true.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: superuser() shortcuts
Next
From: Michael Paquier
Date:
Subject: XLOG_PARAMETER_CHANGE (WAL record) missing two params in its desc routine