Should I forget about getting such a patch in?
I am up for implementing alternative solutions if the current
one is considered unacceptable. As I tried to demonstrate
in my last email, previous attempts also failed.
On Tue, Sep 3, 2019 at 12:14 PM Swen Kooij wrote:
>
> I read two pr
more portable.
[0] https://www.postgresql.org/message-id/511b5d11.4040...@socialserve.com
[1]
https://www.postgresql.org/message-id/bc9ca382-b98d-0446-f699-8c5de2307ca7%402ndquadrant.com
On Tue, Sep 3, 2019 at 9:48 AM Peter Eisentraut
wrote:
>
> On 2019-09-02 22:16, Swen Kooij wrote:
>
> > On 2019-09-02 20:54, Swen Kooij wrote:
> > > I've been working on an extension that tightly integrates
> > > postgres with underlying filesystem . I need to customize
> > > how postgres copies directories for new databases.
> >
> > Could y
I just realized I completely borked the patch file.
My apologies. Attached a (hopefully) correct patch file.
---
Swen Kooij
On Mon, Sep 2, 2019 at 9:54 PM Swen Kooij wrote:
>
> Hello all,
>
> I've been working on an extension that tightly integrates
> postgres with under
s, but I am not entirely sure how to proceed on that front.
I tested my patch extensively against master and
the REL_12_STABLE branch. All tests pass and the patch has
been working great with my extension.
I attached a first draft of the patch against master.
---
Swen Kooij
[1mdiff --git a/src/backe
