29.09.2017 09:50, Ertan Küçükoğlu wrote:
>
> Answer to your question is yes. KAYNAGAGORE and SEBEBEGORE are not
> indexed. Please note that they're not indexed on PostgreSQL, too.
>
> Question remains as how PostgreSQL can cope with identical data only
> with primary key indexes faster than
Hello Dmitry,
Thank you for your time. I just provided a reproducible sample. I'm not trying
to make fine tuning to FirebirdSQL or PostgreSQL.
Answer to your question is yes. KAYNAGAGORE and SEBEBEGORE are not indexed.
Please note that they're not indexed on PostgreSQL, too.
Question remains
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)
Hi,
database structures at:
https://paste.ee/p/qjTwz https://paste.ee/p/qjTwz
Aprox size of tables
Artikli = 227.000 rows
faktur = 85.000 rows
izlaz = 292.000 rows
Partneri = 13400 rows
Kurs = 180 rows
Vrste = 560 rows
Porezi = 6 rows
Faktype = 30 rows
Magacin = 60 rows
Query
SELECT
