Postgres Pro
Downloads
Home   >   mailing lists

Re: Execution time from >1s -> 80m+ when extra columns added inSELECT for sub-query - Mailing list pgsql-performance

From Pavel Stehule
Subject Re: Execution time from >1s -> 80m+ when extra columns added inSELECT for sub-query
Date
Msg-id CAFj8pRCEXjXoxDVXAqNE2qqkEHWM+=ZWHg9qo=soJf0vbK9Y3w@mail.gmail.com
Whole thread Raw
In response to Execution time from >1s -> 80m+ when extra columns added in SELECTfor sub-query  (A Guy Named Ryan <aguynamedryan@gmail.com>)
Responses Re: Execution time from >1s -> 80m+ when extra columns added inSELECT for sub-query  (A Guy Named Ryan <aguynamedryan@gmail.com>)
List pgsql-performance
Tree view
Hi

It looks so in slow plan is some strange relations between subselects - the slow plan looks like plan for correlated subquery, and it should be slow.

Minimally you miss a index on column 
jtemp1c37l3b_baseline_windows_after_inclusion.uuid


pgsql-performance by date:

Previous
From: A Guy Named Ryan
Date:
Subject: Execution time from >1s -> 80m+ when extra columns added in SELECTfor sub-query
Next
From: A Guy Named Ryan
Date:
Subject: Re: Execution time from >1s -> 80m+ when extra columns added inSELECT for sub-query