Hi,
On 2020-02-24 10:29:51 -0800, Mark Dilger wrote:
> > On Feb 20, 2020, at 8:30 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >
> > This idea doesn't fix every possible problem. For instance, if you
> > have a plperlu function that wants to open a bunch of files, I don't
> > see any easy way to ensure we release VFDs to make that possible.
> > But it's sure an improvement on the status quo.
>
> I understand that you were using plperlu just as an example, but it
> got me thinking. Could we ship a wrapper using perl's tie() mechanism
> to call a new spi function to report when a file handle is opened and
> when it is closed? Most plperlu functions would not participate,
> since developers will not necessarily know to use the wrapper, but at
> least they could learn about the wrapper and use it as a work-around
> if this becomes a problem for them. Perhaps the same spi function
> could be used by other procedural languages.
While we're thinking a bit outside of the box: We could just dup() a
bunch of fds within fd.c to protect fd.c's fd "quota". And then close
them when actually needing the fds.
Not really suggesting that we go for that, but it does have some appeal.
> I can't see this solution working unless the backend can cleanup properly under exceptional conditions, and decrement
thecounter of used file handles appropriately. But that's the same requirement that postgres_fdw would also have,
right? Would the same mechanism work for both?
We can just throw an error, and all fdw state should get cleaned up. We
can't generally rely on that for plperl, as it IIRC can global state. So
I don't think they're in the same boat.
Greetings,
Andres Freund