On Wed, 2 Sept 2026 at 06:05, Masahiko Sawada <[email protected]> wrote: > > On Tue, Sep 1, 2026 at 4:55 AM Amit Kapila <[email protected]> wrote: > > > > Agreed that the allocation of more than 1GB for a single row is our > > limitation besides the bug-fix patch we are discussing as can be seen > > by both INSERT/UPDATE cases. Though UPDATE case is slightly different > > as there we are generating such a large tuple (by fetching the entire > > toast tuple data to WAL log as old_tuple) for the REPLICA IDENTIFY > > FULL case, so one could expect it to work. So, if we want to leave > > this limitation for UPDATE/INSERT as it is and just document it (if > > not documented already) then it is okay to proceed with the current > > approach to fix the issue reported by adding another case to the > > limitation. > > +1 >
Added a documentation to mention about this limitation, the attached v6 version patch has the changes for the same. Regards, Vignesh
v6-0001-Log-unchanged-out-of-line-columns-for-row-filtere.patch
Description: Binary data
