Re: Fdw cleanup - Mailing list pgsql-hackers

From Albe Laurenz
Subject Re: Fdw cleanup
Date
Msg-id A737B7A37273E048B164557ADEF4A58B5377557A@ntex2010a.host.magwien.gv.at
Whole thread Raw
In response to Fdw cleanup  (Feng Tian <ftian@vitessedata.com>)
Responses Re: Fdw cleanup  (Feng Tian <ftian@vitessedata.com>)
List pgsql-hackers
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(...);
> 
> If everything goes well, ExecEndForeignScan will call call my EndForeignScan hook, inside the hook, I
> free the resource.
> 
> free_resource(node->fdw_state);
> 
> However, if during the execution an error happened, seems to me that EndForeignScan will not be called
> (traced using gdb).   So my question is, is Begin/End the right place for allocate/free resources?
> If it is not, what is the right way to do this?

If the resource is memory, use "palloc" to allocate it, and PostgreSQL
will take care of it automatically.

Other than that, you could call RegisterXactCallback() and register a callback
that will be called upon transaction end.  In the callback function you can
free the resource if it was not already freed by EndForeignScan.

Yours,
Laurenz Albe

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [PATCH] Logical decoding support for sequence advances
Next
From: Amit Kapila
Date:
Subject: Re: W-TinyLfu for cache eviction