Re: increasing effective_cache_size slows down join queries by a factor of 4000x - Mailing list pgsql-general

From Michael Lewis
Subject Re: increasing effective_cache_size slows down join queries by a factor of 4000x
Date
Msg-id CAHOFxGqBXyC_OjrNbekaQGKC6=Xo-ac5L-aJxS5QASAsSVRyJg@mail.gmail.com
Whole thread Raw
In response to increasing effective_cache_size slows down join queries by a factor of 4000x  (Artyom Shaposhnikov <artyom@gmail.com>)
Responses Re: increasing effective_cache_size slows down join queries by a factor of 4000x  (Artyom Shaposhnikov <artyom@gmail.com>)
List 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)

pgsql-general by date:

Previous
From: Artyom Shaposhnikov
Date:
Subject: increasing effective_cache_size slows down join queries by a factor of 4000x
Next
From: Shaozhong SHI
Date:
Subject: Can Postgres beat Oracle for regexp_count?