IIUC, forcibly written fpws are not exposed to user , so is it worthwhile to
add a GUC similar to full_page_writes in order to control a feature which is
unexposed to user in first place?

If full page writes is set ‘off’ by user, user probably cannot afford the
overhead involved in writing large pages to disk . So , if a full page write
is forcibly written in such a situation it is better to compress it before
writing to alleviate the drawbacks of writing full_page_writes in servers
with heavy write load.

The only scenario in which a user would not want to compress forcibly
written pages is when CPU utilization is high. But according to measurements
done earlier the CPU utilization  of compress=’on’ and ‘off’ are not
significantly different.  

View this message in context: 
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to