| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Nagaraj Raj <nagaraj(dot)sf(at)yahoo(dot)com> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: simple query running for ever |
| Date: | 2020-06-16 22:05:26 |
| Message-ID: | 20200616220526.GK20404@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Jun 16, 2020 at 08:35:31PM +0000, Nagaraj Raj wrote:
> I wrote a simple query, and it is taking too long, not sure what is wrong in it, even its not giving EXPLAIN ANALYZE.
>
> select T0."physical_address_sid", T0."individual_entity_proxy_id", T2."infrrd_hh_rank_nbr"
> from "cms_prospects".PROSPECT T0
> --inner join "sas_prs_tmp".DEDUPE3583E3F18 T1 on T0."individual_entity_proxy_id" = T1."individual_entity_proxy_id"
> left join "cms_prospects".INDIVIDUAL_DEMOGRAPHIC T2 on T0."individual_entity_proxy_id" = T2."individual_entity_proxy_id"
Pardon me for saying so, but this query seems silly.
It's self-joining a table on its PK, which I don't think could ever be useful.
You do maybe more than 2x as much work, to get 2x as many columns, which are
all redundant.
Can't you just change
T2."infrrd_hh_rank_nbr" to T0, and avoid the join ?
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2020-06-16 22:10:37 | Re: simple query running for ever |
| Previous Message | Nagaraj Raj | 2020-06-16 21:15:58 | Re: simple query running for ever |