Re: increasing effective_cache_size slows down join queries by a factor of 4000x

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Artyom Shaposhnikov <artyom(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: increasing effective_cache_size slows down join queries by a factor of 4000x
Date: 2022-02-02 19:46:39
Message-ID: CAHOFxGqBXyC_OjrNbekaQGKC6=Xo-ac5L-aJxS5QASAsSVRyJg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

What does the row estimate look like on the scan of data table with that
statistic in place? Anytime the stats give a mis-estimate this far off, I
wouldn't expect that plans would be optimal except by luck.

Index Scan using data_pkey on data t (cost=0.57..21427806.53 *rows=58785023*
width=131) (actual time=0.024..0.482 *rows=854 *loops=1)
Index Cond: (id > 205284974)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Shaozhong SHI 2022-02-02 20:20:31 Can Postgres beat Oracle for regexp_count?
Previous Message Artyom Shaposhnikov 2022-02-02 19:05:02 increasing effective_cache_size slows down join queries by a factor of 4000x