| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Bryce Nesbitt <bryce2(at)obviously(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | 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:33:58 |
| Message-ID: | 479976363.4147919.1425666838340.JavaMail.yahoo@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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? If you do not have
a sufficiently aggressive vacuum regimen you will have far worse
problems somewhere down the road. You can probably tune autovacuum
to minimize the problems you described. You could also supplement
autovacuum with scheduled VACUUM commands (or possibly even replace
autovacuum with such commands if you are *very* careful). Just
turning off autovacuum is roughly the equivalent of trying to keep
vehicles on the road for more time by skipping all oil changes and
other maintenance. It will appear to work really well for some
amount of time.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-03-06 18:34:09 | Re: BUG #12050: Orphaned base files |
| Previous Message | Bryce Nesbitt | 2015-03-06 17:57:56 | Re: BUG #12834: Avoiding Disk Control Writes for better Laptop / SSD compatibility. pgstats |