Re: Remove unused fields in ReorderBufferTupleBuf
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Aleksander Alekseev <aleksander@timescale.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Masahiko Sawada <sawada.mshk@gmail.com>
Date: 2024-01-22T11:02:00Z
Lists: pgsql-hackers
On Wed, Jul 26, 2023 at 7:22 PM Aleksander Alekseev <aleksander@timescale.com> wrote: > > > Here is the corrected patch. I added it to the nearest CF [1]. > > I played a bit more with the patch. There was an idea to make > ReorderBufferTupleBufData an opaque structure known only within > reorderbyffer.c but it turned out that replication/logical/decode.c > accesses it directly so I abandoned that idea for now. > > > Alternatively we could convert ReorderBufferTupleBufData macro to an > > inlined function. At least it will add some type safety. > > Here is v3 that implements it too as a separate patch. > But why didn't you pursue your idea of getting rid of the wrapper structure ReorderBufferTupleBuf which after this patch will have just one member? I think there could be hassles in backpatching bug-fixes in some cases but in the longer run it would make the code look clean. -- With Regards, Amit Kapila.
Commits
-
Remove ReorderBufferTupleBuf structure.
- 08e6344fd642 17.0 landed
-
Generational memory allocator
- a4ccc1cef5a0 11.0 cited