On Fri, 13 Sep 2019 at 22:01, Robert Haas <robertmh...@gmail.com> wrote: > On Fri, Sep 13, 2019 at 12:14 PM Tom Lane <t...@sss.pgh.pa.us> wrote: > > Again, though, the advice that's been given here is that we should > > fix logical decoding to use the VFD API as it stands, not change > > that API. I concur with that. > > A reasonable position. So I guess logical decoding has to track the > file position itself, but perhaps use the VFD layer for managing FD > pooling.
Yeah, something like the attached patch. I think this tracking of offsets would have been cleaner if we add in-built support in VFD. But yeah, for bank branches at least, we need to handle it outside of VFD. Or may be we would add it if we find one more use-case. -- Thanks, -Amit Khandekar EnterpriseDB Corporation The Postgres Database Company
use_vfd_for_logrep.patch
Description: Binary data
