Re: Slow query fixed by replacing equality with a nested query

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Slow query fixed by replacing equality with a nested query
From: Michael Lewis <mlewis@xxxxxxxxxxx>
Date: Thu, 20 Jan 2022 20:33:17 -0700
Cc: pgsql-performance@xxxxxxxxxxxxxx
In-reply-to: <CAPhGPA5OYUN8m6R=Z429BVBYTpYMvXqhSG3ZbZECpcEyjaDWvQ@mail.gmail.com>
References: <CAPhGPA5OYUN8m6R=Z429BVBYTpYMvXqhSG3ZbZECpcEyjaDWvQ@mail.gmail.com>

I don't see any reference to cte1. Is that expected?

I'm unclear why these sets are not just inner join'd on resource_surrogate_id. It seems like that column it is being selected as Sid1 in each CTE, and then the next one does the below. Why?

where resource_surrogate_id IN (SELECT Sid1 FROM cte_previous_number)

Follow-Ups:
- RE: Slow query fixed by replacing equality with a nested query
  - From: val.janeiko

References:
- Slow query fixed by replacing equality with a nested query
  - From: Valentin Janeiko

Prev by Date: Re: PostgreSQL and Linux CPU's
Next by Date: RE: Slow query fixed by replacing equality with a nested query
Previous by thread: Slow query fixed by replacing equality with a nested query
Next by thread: RE: Slow query fixed by replacing equality with a nested query
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux