Date: Tue, 19 Dec 2017 16:55:57 -0600
From: Justin Pryzby <pryzby@telsasoft.com>
To: Habib Nahas <habibnahas@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Autoanalyze CPU usage
Message-ID: <20171219225557.GG18184@telsasoft.com>
References: 
 <CAE1bBP4vxmMxtC0w37OhDv36M9f8222AbXfy0LWnynWf88ZS-Q@mail.gmail.com>
 <20171219170958.GF18184@telsasoft.com>
 <CAE1bBP5GijFE+XHbLD9NH87o7r98aA=c3_eLOC4a4-xYP1hv8A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAE1bBP5GijFE+XHbLD9NH87o7r98aA=c3_eLOC4a4-xYP1hv8A@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk

On Tue, Dec 19, 2017 at 02:37:18PM -0800, Habib Nahas wrote:
> As it happens our larger tables operate as a business log and are also
> insert only.
> 
> - There is no partitioning at this time since we expect to have an
> automated process to delete rows older than a certain date.

This is a primary use case for partitioning ; bulk DROP rather than DELETE.

> - Analyzing doing off-hours sounds like a good idea; if there is no other
> way to determine effect on db we may end up doing that.

You can also implement a manual analyze job and hope to avoid autoanalyze.

> - We have an open schema and heavily depend on jsonb, so I'm not sure if
> increasing the statistics target will be helpful.

If the increased stats target isn't useful for that, I would recommend to
decrease it.

-- 
Justin Pryzby
System Administrator
Telsasoft
+1-952-707-8581