Subject Re: Firebird performance vs PostgreSQL
Author Dmitry Yemanov
29.09.2017 01:08, Ertan Küçükoğlu wrote:

Answers can be found in the plans:

> PLAN JOIN (RAPOR_EK ORDER rapor_ek_pkey, SORT (DT M NATURAL))

This join plan is terrible for FB. Are KAYNAGAGORE and SEBEBEGORE
indexed? They seem not.

> Merge Left Join (cost=6600.19..6610.98 rows=560 width=340)

FB cannot perform merge- or hash-join for outer joins (yet). When
important indices are missing, this becomes a problem.


Dmitry