Re: BUG #12834: Avoiding Disk Control Writes for better Laptop / SSD compatibility. pgstats

On Fri, Mar 6, 2015 at 6:19 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:

> Use "SHOW autovacuum" in psql to avoid being confounded by
> mind-controlling superpowers.
>

Indeed. My mistake. Autovac *was* the droid I was looking for. On orders
of the Empire, that droid has been eliminated on twenty five laptops.
Millions more exist however, each chewing through the write cycles on SSD's
in a futile attempt to bring down the social order.

--
More seriously: I've been cataloguing what churns the SSD at idle. The top
two are Google Chrome's constant rewriting of HTML5 Local Storage elements,
and PostgreSQL. This is true both in terms of raw writes and blocks
written. It's a significant fraction of the SSD's life (some 40% in the
first laptop analyzed above).

This will never show up in a PostgreSQL benchmark, and never cause a
problem for the PSQL team. But it's eating through SSD's wherever default
mode Postgres is installed but not heavily used.