Re: simple query running for ever
От
Laurenz Albe
Тема
Re: simple query running for ever
Дата
Msg-id
832b7c51f310e5d9fc35f5f1310a736dba4422a3.camel@cybertec.at
Ответ на
simple query running for ever (Nagaraj Raj)
Список
Дерево обсуждения
simple query running for ever Nagaraj Raj <nagaraj.sf@yahoo.com>
Re: simple query running for ever Justin Pryzby <pryzby@telsasoft.com>
Re: simple query running for ever Nagaraj Raj <nagaraj.sf@yahoo.com>
Re: simple query running for ever Justin Pryzby <pryzby@telsasoft.com>
Re: simple query running for ever Andreas Joseph Krogh <andreas@visena.com>
Re: simple query running for ever Justin Pryzby <pryzby@telsasoft.com>
Re: simple query running for ever Laurenz Albe <laurenz.albe@cybertec.at>
Re: simple query running for ever Michael Lewis <mlewis@entrata.com>
Re: simple query running for ever Nagaraj Raj <nagaraj.sf@yahoo.com>
Re: simple query running for ever Nagaraj Raj <nagaraj.sf@yahoo.com>
On Tue, 2020-06-16 at 20:35 +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" > > > "Merge Left Join (cost=55.96..18147747.08 rows=213620928 width=20)" > " Merge Cond: (t0.individual_entity_proxy_id = t2.individual_entity_proxy_id)" > " -> Index Scan using pk_prospect on prospect t0 (cost=0.57..10831606.89 rows=213620928 width=16)" > " -> Index Only Scan using indxp_individual_demo_infrrd_hh_rank_nbr on individual_demographic t2 (cost=0.57..5013756.93 rows=260652064 width=12)" > > > > Any suggestions or help would be highly appreciated. The only potential improvement I can see is to strive for an "index only scan" on "prospect". For that, you'd have to add and INCLUDE clause to "pk_prospect" so that "physical_address_sid" and "individual_entity_proxy_id" are included and VACUUM the table. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com
В списке pgsql-performance по дате отправления