Search Postgresql Archives

Join optimization

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

 



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-services.com/the-myth-of-nosql-vs-rdbms-joins-dont-scale/
[2]  https://dbfiddle.uk/?rdbms=oracle_18&fiddle=a5afeba2fdb27dec7533545ab0a6eb0e
[3]  https://dbfiddle.uk/?rdbms=postgres_13&fiddle=87c78b4e97fdbd87255efc2fc909ee62

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux