Re: autovacuum can't keep up, bloat just continues to rise

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>, Sokolov Yura <y(dot)sokolov(at)postgrespro(dot)ru>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers-owner(at)postgresql(dot)org
Subject: Re: autovacuum can't keep up, bloat just continues to rise
Date: 2017-07-20 14:11:20
Message-ID: 93ebede7-e26e-c343-03b7-a5030a9d80c7@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07/20/2017 06:28 AM, Stephen Frost wrote:

> It's not clear off-hand how much that would improve this case, as
> the database size appears to pretty quickly get beyond the OS memory
> size (and only in the first test is the DB starting size less than
> system memory to begin with).

FYI,

I will be posting new numbers in a few hours. I had been planning on
posting this last night but... KDE.

JD

--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc

PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.us
***** Unless otherwise stated, opinions are my own. *****

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2017-07-20 14:24:24 Re: JSONB - JSONB operator feature request
Previous Message Michael Paquier 2017-07-20 14:07:16 Re: Cache lookup errors with functions manipulation object addresses