Re: Why PG uses nested-loop join when no indexes are available?

Поиск
Список
Период
Сортировка
От David Grelaud
Тема Re: Why PG uses nested-loop join when no indexes are available?
Дата
Msg-id CABKm3pggjf_Bo7hd9nvG3SwizXcynE+0ANFfp54GYrOQQYCzyQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Why PG uses nested-loop join when no indexes are available?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
Дерево обсуждения
Thank you for your fast response!

I'm sorry, my vocabulary may be not correct and my "french approach" to explain my problem is not efficient ;).

But the underestimation problem in complex queries is still there? ... and generates potential "dangerous" plans (nested loop).

We thought at the beginning we were alone but it seems to be a problem of most database systems.
What do you think about the paragraph 4.1 of this paper  http://www.vldb.org/pvldb/vol9/p204-leis.pdf ?

Regards,
-------------------
David Grelaud,
Ideolys.



2016-01-13 16:02 GMT+01:00 Tom Lane <tgl@sss.pgh.pa.us>:
David Grelaud <dgrelaud@ideolys.com> writes:
> Statistics are not propagated when Common Table Expressions (CTE) are used.
> The cardinality of a CTE is equal to 1 most of the time

Really?

The rest of this seems to be proceeding from completely false assumptions.

                        regards, tom lane

В списке pgsql-general по дате отправления:

Предыдущее
От: Jim Nasby
Дата:
Сообщение: Re: Call postgres PL/Python stored function from another PL/Python block.
Следующее
От: Vick Khera
Дата:
Сообщение: Re: Moving a large DB (> 500GB) to another DB with different locale