Re: Async execution of postgres_fdw. - Mailing list pgsql-hackers

From Matt Kelly
Subject Re: Async execution of postgres_fdw.
Date
Msg-id CA+KcUkhLUo+Vaj4xR8GVsof_nW79uDZTDYhOSdt13CFJkaEEdQ@mail.gmail.com
Whole thread Raw
In response to Re: Async execution of postgres_fdw.  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: Async execution of postgres_fdw.
List 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 by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: B-Tree support function number 3 (strxfrm() optimization)
Next
From: Abhijit Menon-Sen
Date:
Subject: Re: pgaudit - an auditing extension for PostgreSQL