| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | "Dean Gibson (DB Administrator)" <postgresql(at)mailpen(dot)com> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Date: | 2021-05-31 03:41:28 |
| Message-ID: | 2370D2C6-4D91-4C96-9410-11EFD9954B21@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
> On May 30, 2021, at 20:07, Dean Gibson (DB Administrator) <postgresql(at)mailpen(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2021-05-31 03:52:54 | Re: pg_get_wal_replay_pause_state() should not return 'paused' while a promotion is ongoing. |
| Previous Message | Michael Paquier | 2021-05-31 03:33:51 | Re: Multiple hosts in connection string failed to failover in non-hot standby mode |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Gibson (DB Administrator) | 2021-05-31 04:23:43 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Previous Message | Dean Gibson (DB Administrator) | 2021-05-31 03:07:29 | Re: AWS forcing PG upgrade from v9.6 a disaster |