Add support for the async_capable option to allow async fetching of result sets, as described in All Your GUCs in a Row: enable_async_append and the FDW Routines for Asynchronous Execution docs. The option was added to postgres_fdw in postgres/postgres@27e1f1456 and modified in postgres/postgres@bb684c82 and postgres/postgres@5c854e7.
This will allow Postgres to execute fetches via pg_clickhouse asynchronously with other foreign tables, via pg_clickhouse or otherwise. Note, however, that its utility will be limited for fetches from the same foreign server, as pg_clickhouse uses a a single connection for all queries for a given server, so they'll run synchronously. Thus this feature, while desirable, is less important than improving join pushdown in general.
Suggested by @heavycrystal.
Add support for the
async_capableoption to allow async fetching of result sets, as described in All Your GUCs in a Row:enable_async_appendand the FDW Routines for Asynchronous Execution docs. The option was added to postgres_fdw in postgres/postgres@27e1f1456 and modified in postgres/postgres@bb684c82 and postgres/postgres@5c854e7.This will allow Postgres to execute fetches via pg_clickhouse asynchronously with other foreign tables, via pg_clickhouse or otherwise. Note, however, that its utility will be limited for fetches from the same foreign server, as pg_clickhouse uses a a single connection for all queries for a given server, so they'll run synchronously. Thus this feature, while desirable, is less important than improving join pushdown in general.
Suggested by @heavycrystal.