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.
regards, tom lane
