On Tue, Apr 22, 2025 at 7:20 PM Tom Lane <t...@sss.pgh.pa.us> wrote: > Alexander Korotkov <aekorot...@gmail.com> writes: > > I'd like to add that float4.out not only assumes that insert-ordering is > > preserved (this could be more-or-less portable between table AMs). It also > > assumes the way UPDATE moves updated rows. That seems quite > > heap-specific. You can see in the following fragment, updated rows jump to > > the bottom. > > I'd be willing to consider a policy that we don't want to depend on > exactly where UPDATE moves rows to. The proposed patch is not that, > however.
OK, that makes sense for me. ------ Regards, Alexander Korotkov Supabase
