Re: Avoiding out of date statistics / planner
От | Tomas Vondra |
---|---|
Тема | Re: Avoiding out of date statistics / planner |
Дата | |
Msg-id | 20200212203245.yuilq66zbxu3iv7d@development обсуждение исходный текст |
Ответ на | Re: Avoiding out of date statistics / planner (Michael Lewis <mlewis@entrata.com>) |
Ответы |
Re: Avoiding out of date statistics / planner
|
Список | pgsql-general |
On Wed, Feb 12, 2020 at 10:23:22AM -0700, Michael Lewis wrote: >It may also be worth noting that it is possible to make autovacuum/analyze >more aggressive, perhaps only on the tables that see large changes in data >that might result in a statistics issue. If you could share a query, >explain analyze output, and pseudo code or at least description of what >sort of bulk operations are being done, then more insight could be offered. Another thing you can do is deploy auto_explain, and log explain plan for long-runnning queries. That won't fix the root cause, but it will help you with confirming the root cause - you'll see the query plan, which should give you enough context. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-general по дате отправления: