Re: Join optimization

From: Fabrízio de Royes Mello <fabrizio(at)timbira(dot)com(dot)br>
To: luis(dot)roberto(at)siscobra(dot)com(dot)br
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Join optimization
Date: 2020-07-11 18:24:04
Message-ID: CAPfkCSC-NmtwZVe5Q=KLVdk6V-b1OYS9XefbccizHuS37c4g1Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Em sáb, 11 de jul de 2020 às 14:20, <luis(dot)roberto(at)siscobra(dot)com(dot)br> escreveu:

> Hi!
>
> Recently on a blogpost [1] I saw that Oracle was able to "optimize" a join
> strategy by completely eliminating access to a table.
>
> Heres the execution on Oracle 18c [2] and PostgreSQL 13 (beta) [3].
>
> Is there a fundamental reason why PG can't do the same?
>

It does... did you see the “never executed” notice on the Postgres explain
output?

Regards,

--
Fabrízio de Royes Mello Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message luis.roberto 2020-07-11 18:59:24 Re: Join optimization
Previous Message Brian Dunavant 2020-07-11 17:43:54 Re: Listen/Notify feedback