Hi,

On Sat, Jun 27, 2026 at 1:54 AM Bharath Rupireddy
<[email protected]> wrote:
>
> Please find the attached v3 patch for further review. I would be happy
> to split this patch into two if necessary.

Upon thinking about this more, I would like to withdraw this from the
CF unless anyone thinks otherwise. I realize that testing resources
are not free. Also, the patch was not trying to fix a bug or improve
performance, and the change is not in a hot code path (concurrent
updates on the subscriber are relatively rare). Even if it were the
most common case, allocating a slot and materializing the tuple into a
new slot surely won't show up in perf profiles among other costs such
as applying the changes, waiting for tuples to be received from the
publisher, etc. So, I don't think it's worth the effort.

Thanks, and sorry for the noise.

-- 
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com


Reply via email to