Re: Huge shared hit for small table
От | Jeff Janes |
---|---|
Тема | Re: Huge shared hit for small table |
Дата | |
Msg-id | CAMkU=1zjDKdXaFSihtqsRhc5RjjqC8Vr_B-RsPqf9p_UQVMS9A@mail.gmail.com обсуждение исходный текст |
Ответ на | Huge shared hit for small table (Scott Rankin <srankin@motus.com>) |
Ответы |
Re: Huge shared hit for small table
Re: Huge shared hit for small table |
Список | pgsql-performance |
Hello all,
We are trying to debug some slow performance in our production environment (Amazon RDS, Postgresql 9.6.11), and we’re looking at a particular EXPLAIN node that seems… weird. This is a very large query involving a number of joins, but it performs pretty well in our staging environment (which has roughly the same data set as production, with a few tweaks). However, there is one node in the EXPLAIN plan that is wildly different:
The tables in both environments are about the same size (18MB) and the indexes are about the same size (360kb/410kb) – and the shared hits are pretty much the same on the other nodes of the query between the two environments.
This has happened one time before, and we did a “REINDEX” on the program table – and that made the problem mostly go away. Now it seems to be back, and I’m not sure what to make of it.
В списке pgsql-performance по дате отправления: