Hi, Albe,
Thank you.
The resource is not memory, I have something like a file descriptor or
network connection, which I believe is the common case for foreign table.
Using RegisterXactCallback exposes an API at a much deep level to foreign
table writer, and I need to find a place to anchor the
Feng Tian wrote:
> I need some help to understand foreign table error handling.
>
> For a query on foreign table, ExecInitForeignScan is called, which in turn
> calls the BeginForeignScan
> hook. Inside this hook, I allocated some resource,
>
>
> node->fdw_state = allocate_resource(...);
>
Hi, Hackers,
I need some help to understand foreign table error handling.
For a query on foreign table, ExecInitForeignScan is called, which in turn
calls the BeginForeignScan hook. Inside this hook, I allocated some
resource,
node->fdw_state = allocate_resource(...);
If everything goes
