From: Justin Pryzby <pryzby@telsasoft.com>
To: Habib Nahas <habibnahas@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Autoanalyze CPU usage
Date: Tue, 19 Dec 2017 16:55:57 -0600
Message-ID: <20171219225557.GG18184@telsasoft.com> (raw)
In-Reply-To: <CAE1bBP5GijFE+XHbLD9NH87o7r98aA=c3_eLOC4a4-xYP1hv8A@mail.gmail.com>
References: <CAE1bBP4vxmMxtC0w37OhDv36M9f8222AbXfy0LWnynWf88ZS-Q@mail.gmail.com>
<20171219170958.GF18184@telsasoft.com>
<CAE1bBP5GijFE+XHbLD9NH87o7r98aA=c3_eLOC4a4-xYP1hv8A@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pryzby@telsasoft.com, habibnahas@gmail.com, pgsql-performance@lists.postgresql.org
Subject: Re: Autoanalyze CPU usage
In-Reply-To: <20171219225557.GG18184@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox