Re: How to use brin_summarize_range

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Jeremy Finzel <finzelj(at)gmail(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: How to use brin_summarize_range
Date: 2019-08-23 21:38:17
Message-ID: CAHOFxGrY5gmUSC-DGyUQY6oXLJbffJOC8X-xQQiBseo18_LueQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

What is default_statistics_target set to? Or is there custom statistics
value set for this table/column? Perhaps the planner is making sub-optimal
choices because it only has a vague idea about the data and the histogram
is not very informative. Planning time will increase when statistics target
is increased, but perhaps 250 instead of default 100 would give *enough*
more information to make better choices. Or perhaps your target is already
max 10000 and then I have no idea why btree would be chosen. Except, if
correlation is too low for the optimizer to consider BRIN to be best
perhaps. What does pg_stats say about the column in question?

>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message PegoraroF10 2019-08-23 21:47:55 Re: slow queries on system tables
Previous Message Georg H. 2019-08-23 21:00:10 Re: Question on pgwatch