Re: Attempt to consolidate reading of XLOG page - Mailing list pgsql-hackers

From Haribabu Kommi
Subject Re: Attempt to consolidate reading of XLOG page
Date
Msg-id CAJrrPGcdQTfNhXPoYthqjmxvk1YbHPDDP+fwsXQUQqUL2yRJPA@mail.gmail.com
Whole thread Raw
In response to Attempt to consolidate reading of XLOG page  (Antonin Houska <ah@cybertec.at>)
List pgsql-hackers

On Fri, Apr 12, 2019 at 2:06 AM Antonin Houska <ah@cybertec.at> wrote:
While working on the instance encryption I found it annoying to apply
decyption of XLOG page to three different functions. Attached is a patch that
tries to merge them all into one function, XLogRead(). The existing
implementations differ in the way new segment is opened. So I added a pointer
to callback function as a new argument. This callback handles the specific
ways to determine segment file name and to open the file.

I can split the patch into multiple diffs to make detailed review easier, but
first I'd like to hear if anything is seriously wrong about this
design. Thanks.

I didn't check the code, but it is good to combine all the 3 page read functions
into one instead of spreading the logic.

Regards,
Haribabu Kommi
Fujitsu Australia

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: improve PQexec documentation
Next
From: Haribabu Kommi
Date:
Subject: Transparent data encryption support as an extension