> On May 30, 2021, at 20:07, Dean Gibson (DB Administrator) > <postgre...@mailpen.com> wrote: > The first two JOINs are not the problem, & are in fact retained in my > solution. The problem is the third JOIN, where "fips_county" from "County" > is actually matched with the corresponding field from the "zip_code" VIEW. > Works fine, if you don't mind the performance impact in v10 & above. It has > now been rewritten, to be a sub-query for an output field. Voila ! Back to > sub-second query times. If, rather than a subquery, you explicitly called out the join criteria with ON, did it have the same performance benefit?
- Re: AWS forcing PG upgrade fro... Andrew Dunstan
- Re: AWS forcing PG upgrade... Jan Wieck
- Re: AWS forcing PG upgrade from v9.6 a... Dean Gibson (DB Administrator)
- Re: AWS forcing PG upgrade from v9.6 a disa... Dean Gibson (DB Administrator)
- Re: AWS forcing PG upgrade from v9.6 a... Andrew Dunstan
- Re: AWS forcing PG upgrade from v9... Dean Gibson (DB Administrator)
- Re: AWS forcing PG upgrade fro... Andrew Dunstan
- Re: AWS forcing PG upgrade... Dean Gibson (DB Administrator)
- Re: AWS forcing PG upgrade from v9.6 a disa... Dean Gibson (DB Administrator)
- Re: AWS forcing PG upgrade from v9.6 a disa... Dean Gibson (DB Administrator)
- Re: AWS forcing PG upgrade from v9.6 a... Christophe Pettus
- Re: AWS forcing PG upgrade from v9... Dean Gibson (DB Administrator)
- Re: AWS forcing PG upgrade fro... Tom Lane
- Re: AWS forcing PG upgrade... Dean Gibson (DB Administrator)
- Re: AWS forcing PG upgrade from v9.6 a... Justin Pryzby
- Re: AWS forcing PG upgrade from v9... Dean Gibson (DB Administrator)
- Re: AWS forcing PG upgrade fro... Dean Gibson (DB Administrator)
- Re: AWS forcing PG upgrade... Andrew Dunstan
- Re: AWS forcing PG up... Dean Gibson (DB Administrator)
- Re: AWS forcing P... Ranier Vilela
- Re: AWS forcing P... Dean Gibson (DB Administrator)