Re: making tid and HOTness of UPDATE available to logical decoding plugins

2025-12-05 Thread Hannu Krosing
On Fri, Dec 5, 2025 at 3:58 PM Euler Taveira wrote: > > On Thu, Dec 4, 2025, at 5:58 PM, Hannu Krosing wrote: > > Please find attached a patch that makes tuple ids and info about > > weather it was plain or HOT update available to logical decoding > > callbacks. > > > > My first impression was: wh

Re: making tid and HOTness of UPDATE available to logical decoding plugins

2025-12-05 Thread Euler Taveira
On Thu, Dec 4, 2025, at 5:58 PM, Hannu Krosing wrote: > Please find attached a patch that makes tuple ids and info about > weather it was plain or HOT update available to logical decoding > callbacks. > My first impression was: why do you want to expose an internal information that is mostly usele

Re: making tid and HOTness of UPDATE available to logical decoding plugins

2025-12-05 Thread Hannu Krosing
On Thu, Dec 4, 2025 at 11:35 PM Mihail Nikalayeu wrote: > > Hello! > > Thanks for the patch. Thanks for reviewing :) > Few comments: > > 1) tests are failing, expected output files need to be updated Yes, I didn't want to start changing tests before other parts stabilized a bit. > 2) > > * Tre

Re: making tid and HOTness of UPDATE available to logical decoding plugins

2025-12-04 Thread Mihail Nikalayeu
Hello! Thanks for the patch. Few comments: 1) tests are failing, expected output files need to be updated 2) > * Treat HOT update as normal updates. There is no useful > * information in the fact that we could make it a HOT update > * locally and the WAL layout is compatible. I think it feels

making tid and HOTness of UPDATE available to logical decoding plugins

2025-12-04 Thread Hannu Krosing
Please find attached a patch that makes tuple ids and info about weather it was plain or HOT update available to logical decoding callbacks. Also modified test_decoding to show both tids - - old tid has format -(pageno, slot) - new tid has format +(pageno, slot) if it is a HOT update, it is decode