Re: Avoiding out of date statistics / planner

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tim Kane <tim(dot)kane(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: Avoiding out of date statistics / planner
Date: 2020-02-12 17:23:22
Message-ID: CAHOFxGoLmmZCkP=zMpV7mTJk5Rqhprtw=rQkj6-bWK5ZwQMLUw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andres Freund 2020-02-12 19:42:21 Re: JIT on Windows with Postgres 12.1
Previous Message Dmitry Igrishin 2020-02-12 17:14:36 Re: Natural sort order extension.