Re: AWS forcing PG upgrade from v9.6 a disaster

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Lionel Bouton <lionel(dot)bouton(at)jtek(dot)fr>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: AWS forcing PG upgrade from v9.6 a disaster
Date: 2021-05-29 22:34:57
Message-ID: CAHOFxGpJx6=W0ADLr9UFjSdPDF4OyOzm2mwhXWQkKB9N5MQ8zA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-performance

On Sat, May 29, 2021, 4:40 AM Lionel Bouton <lionel(dot)bouton(at)jtek(dot)fr> wrote:

> The last time I had to use this setting to solve this kind of problem I
> ended with :
>
> default_statistics_target = 500
>
> But obviously the value suited to your case could be different (I'd
> increase it until the planner uses the correct index). Note that increasing
> it increases the costs of maintaining statistics (so you don't want to
> increase this by several orders of magnitude blindly) but the default value
> seems fairly conservative to me.
>

It also increases planning time since those distribution statistics need to
be consumed and decisions have to be made.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dean Gibson (DB Administrator) 2021-05-29 22:47:39 Re: AWS forcing PG upgrade from v9.6 a disaster
Previous Message Andrew Dunstan 2021-05-29 20:35:27 Re: AWS forcing PG upgrade from v9.6 a disaster

Browse pgsql-performance by date

  From Date Subject
Next Message Dean Gibson (DB Administrator) 2021-05-29 22:47:39 Re: AWS forcing PG upgrade from v9.6 a disaster
Previous Message Andrew Dunstan 2021-05-29 20:35:27 Re: AWS forcing PG upgrade from v9.6 a disaster