| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fortify float4 and float8 regression tests by ordering test results |
| Date: | 2025-04-22 16:22:10 |
| Message-ID: | CAPpHfdsjK1C7t1SpiRGjFvoFds-XhXqMToRsrcgt4t1c9+OL6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 22, 2025 at 7:20 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alexander Korotkov <aekorotkov(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2025-04-22 16:23:25 | Re: What's our minimum supported Python version? |
| Previous Message | Tom Lane | 2025-04-22 16:20:55 | Re: Fortify float4 and float8 regression tests by ordering test results |