| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Rahila Syed <rahilasyed(dot)90(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [REVIEW] Re: Compression of full-page-writes |
| Date: | 2014-12-05 01:53:35 |
| Message-ID: | CA+TgmoarY=L2GZBbJXmdzSNdozahz12qaf7213htiqurEA3Faw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 4, 2014 at 5:36 AM, Rahila Syed <rahilasyed(dot)90(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2014-12-05 02:54:15 | XLOG_PARAMETER_CHANGE (WAL record) missing two params in its desc routine |
| Previous Message | Robert Haas | 2014-12-05 01:44:54 | Re: superuser() shortcuts |