- Mensagem original -
De: "David Rowley"
Para: "luis.roberto"
Cc: "Fabrízio de Royes Mello" , "pgsql-general"
Enviadas: Domingo, 12 de julho de 2020 5:29:08
Assunto: Re: Join optimization
On Sun, 12 Jul 2020 at 06:59, wrote:
>
> I&#x
On Sun, 12 Jul 2020 at 06:59, wrote:
>
> I'm sorry for the bad example.
>
> Here is another, with some data on PG:
> https://dbfiddle.uk/?rdbms=postgres_13&fiddle=ccfd1c4fa291e74a6db9db1772e2b5ac
> and Oracle:
> https://dbfiddle.uk/?rdbms=oracle_18&fiddle=21a98f499065ad4e2c35ff4bd1487e14.
I
ello"
Para: "luis.roberto"
Cc: "pgsql-general"
Enviadas: Sábado, 11 de julho de 2020 15:24:04
Assunto: Re: Join optimization
Em sáb, 11 de jul de 2020 às 14:20, < [ mailto:luis.robe...@siscobra.com.br |
luis.robe...@siscobra.com.br ] > escreveu:
Hi!
Re
Em sáb, 11 de jul de 2020 às 14:20, 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
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?
Thanks!
[1] [
https://blog.dbi-
