Re: Async execution of postgres_fdw.

Поиск
Список
Период
Сортировка
От Matt Kelly
Тема Re: Async execution of postgres_fdw.
Дата
Msg-id CA+KcUkhLUo+Vaj4xR8GVsof_nW79uDZTDYhOSdt13CFJkaEEdQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Async execution of postgres_fdw.  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Ответы Re: Async execution of postgres_fdw.  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Список pgsql-hackers
I think its telling that varying the fetch size doubled the performance, even on localhost.  If you were to repeat this test across a network, the performance difference would be far more drastic.

I understand the desire to keep the fetch size small by default, but I think your results demonstrate how important the value is.  At the very least, it is worth reconsidering this "arbitrary" value.  However, I think the real solution is to make this configurable.  It probably should be a new option on the foreign server or table, but an argument could be made for it to be global across the server just like work_mem.

Obviously, this shouldn't block your current patch but its worth revisiting.

- Matt Kelly

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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: B-Tree support function number 3 (strxfrm() optimization)
Следующее
От: Abhijit Menon-Sen
Дата:
Сообщение: Re: pgaudit - an auditing extension for PostgreSQL