Re: Duplicate WHERE condition changes performance and plan
От | singh400@gmail.com |
---|---|
Тема | Re: Duplicate WHERE condition changes performance and plan |
Дата | |
Msg-id | CAOtbvR+_tqYfHc1GtPkFsNkffXoecUusxDfj-FJ+o9-aOpZySg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Duplicate WHERE condition changes performance and plan (David Rowley <dgrowleyml@gmail.com>) |
Ответы |
Re: Duplicate WHERE condition changes performance and plan
|
Список | pgsql-performance |
> Starting with PostgreSQL 9.6, foreign keys are also used to help with > join selectivity estimations. I see you have a suitable foreign key > from the schema you posted. You might want to add that to the list of > reasons to upgrade. Apologies for the delay in response. I've had "PostgreSQL 9.6.3, compiled by Visual C++ build 1800, 64-bit" setup at home for a while and after importing the data across I'm still seeing the same behaviour. Even after upgrading my local install of PG to "PostgreSQL 12.2, compiled by Visual C++ build 1914, 64-bit" and I'm still seeing the same behaviour. Plans for PG12:- Query A: https://explain.depesz.com/s/zrVD Query B: https://explain.depesz.com/s/ZLWe The settings for my home setup are left at default, nothing special. Indy
В списке pgsql-performance по дате отправления: