Re: [GENERAL] effective_io_concurrency increasing

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: [GENERAL] effective_io_concurrency increasing
Дата
Msg-id CAH2-Wzkkd4wPzcGDSdzq7NJRXD8jP=BCMu3e4gijEwXN-Qm4ag@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [GENERAL] effective_io_concurrency increasing  (Peter Geoghegan <pg@bowt.ie>)
Список pgsql-general
On Mon, Jun 19, 2017 at 4:51 PM, Peter Geoghegan <pg@bowt.ie> wrote:
> This would make only the first lookup for each distinct value on the
> outer side actually do an index scan on the inner side. I can imagine
> the optimization saving certain queries from consuming a lot of memory
> bandwidth, as well as saving them from pinning and locking the same
> buffers repeatedly.

Apparently this is sometimes called block nested loop join, and MySQL
has had it for a while now:

https://en.wikipedia.org/wiki/Block_nested_loop

It doesn't necessarily require that the outer side input be sorted,
because you might end up using a hash table, etc.

--
Peter Geoghegan


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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: [GENERAL] effective_io_concurrency increasing
Следующее
От: "Maeldron T."
Дата:
Сообщение: [GENERAL] Streaming replication bandwith per table