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

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: John R Pierce <pierce(at)hogranch(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #12834: Avoiding Disk Control Writes for better Laptop / SSD compatibility. pgstats
Date: 2015-03-06 21:57:23
Message-ID: CAGTBQpaB4UbhcZKe4OUhiosxh4+bFjNV_x9tz2LwWVo0yJDeQg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Mar 6, 2015 at 5:45 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 3/6/2015 10:46 AM, Bryce Nesbitt wrote:
>>
>> 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.
>
>
>
> eventually, you HAVE to vacuum for various reasons. you might use a cron
> job (or task scheduler) to setup a weekly job that does a vacuumdb -a).

Or put a naptime of 6h.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jaime Casanova 2015-03-07 00:11:17 Re: [BUGS] compatibilty postgres 9.2 RHEL 6.4
Previous Message John R Pierce 2015-03-06 20:45:01 Re: BUG #12834: Avoiding Disk Control Writes for better Laptop / SSD compatibility. pgstats