Re: logical decoding / rewrite map vs. maxAllocatedDescs - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: logical decoding / rewrite map vs. maxAllocatedDescs
Date
Msg-id 20180809175846.gyycn5rgbo7eksy5@alvherre.pgsql
Whole thread Raw
In response to Re: logical decoding / rewrite map vs. maxAllocatedDescs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2018-Aug-09, Tom Lane wrote:

> It sounds like whoever wrote that code was completely impervious to the
> API spec for AllocateFile():
> 
>  * Note that files that will be open for any significant length of time
>  * should NOT be handled this way, since they cannot share kernel file
>  * descriptors with other files; there is grave risk of running out of FDs
>  * if anyone locks down too many FDs.
> 
> Perhaps these files should be accessed through fd.c's VFD infrastructure
> rather than ignoring it.  Reinventing it is especially not the way to go.

Ah, right.  Maybe ReorderBufferRestoreChanges should use
PathNameOpenFile / FileRead ...

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: xact_start meaning when dealing with procedures?
Next
From: Tomas Vondra
Date:
Subject: Re: logical decoding / rewrite map vs. maxAllocatedDescs