| From: | "singh400(at)gmail(dot)com" <singh400(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Duplicate WHERE condition changes performance and plan |
| Date: | 2020-04-20 00:50:17 |
| Message-ID: | CAOtbvR+_tqYfHc1GtPkFsNkffXoecUusxDfj-FJ+o9-aOpZySg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2020-04-20 02:33:57 | Re: Duplicate WHERE condition changes performance and plan |
| Previous Message | Rick Vincent | 2020-04-17 15:12:14 | RE: Postgres not using index on views |