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

Поиск
Список
Период
Сортировка
От Michael Lewis
Тема Re: increasing effective_cache_size slows down join queries by a factor of 4000x
Дата
Msg-id CAHOFxGqBXyC_OjrNbekaQGKC6=Xo-ac5L-aJxS5QASAsSVRyJg@mail.gmail.com
обсуждение исходный текст
Ответ на increasing effective_cache_size slows down join queries by a factor of 4000x  (Artyom Shaposhnikov <artyom@gmail.com>)
Ответы Re: increasing effective_cache_size slows down join queries by a factor of 4000x  (Artyom Shaposhnikov <artyom@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Artyom Shaposhnikov
Дата:
Сообщение: increasing effective_cache_size slows down join queries by a factor of 4000x
Следующее
От: Shaozhong SHI
Дата:
Сообщение: Can Postgres beat Oracle for regexp_count?