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

From: Bryce Nesbitt <bryce2(at)obviously(dot)com>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #12834: Avoiding Disk Control Writes for better Laptop / SSD compatibility. pgstats
Date: 2015-03-06 18:46:57
Message-ID: CAC9LFPc3xHYq40MWsKh1fgo9qLKUauPKx67GV543sGv8eN_BHg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Mar 6, 2015 at 10:33 AM, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:

> Bryce Nesbitt <bryce2(at)obviously(dot)com> wrote:
>
> > Autovac was the droid I was looking for. On orders of the Empire,
> > that droid has been eliminated on twenty five laptops.
>
> What, exactly, did you do to "eliminate" that?
>

Given the use case on these machines, turning off auto vacuum completely
was appropriate.
The 1 minute vacuum is just fine for an active cluster, but the write churn
on the SSD
was not worth it here. A read only workload would be fine.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message John R Pierce 2015-03-06 20:45:01 Re: BUG #12834: Avoiding Disk Control Writes for better Laptop / SSD compatibility. pgstats
Previous Message Tom Lane 2015-03-06 18:34:09 Re: BUG #12050: Orphaned base files