| From: | Dmitry Kovalenko <d(dot)kovalenko(at)postgrespro(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19338: [PG15] Unstable SQL result in test regress/tablespace |
| Date: | 2025-12-01 16:52:47 |
| Message-ID: | 507b05d3-ecc7-4840-afbd-c5098585f051@postgrespro.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom,
This test worked on the VM with 4GB memory, 2 cores and AltLinux-10 that
is hosted on ARM where are worked lots of other VMs.
I do not know why this select returns wrong order but do not want to see
this problem again.
I think, we see a prove of unstable order of SELECT without ORDER BY
clause )
Regards,
Dmitry Kovalenko
01.12.2025 18:54, Tom Lane пишет:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
>> PG15 has an unstable SQL in test regress/tablespace:
> I tried to reproduce this, without much success. For me, that
> query gives the same EXPLAIN plan and the same results with
> or without ORDER BY. (It chooses an indexscan that'd naturally
> order the results.) And the v15 regression tests pass fine in
> a few different locales I tried, which doesn't surprise me
> given the lack of prior complaints.
>
> In short, I think there's more going on here than meets the eye.
> Can you give a recipe for reproducing this failure?
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2025-12-01 20:11:16 | BUG #19339: odbc_fdw extension, Not able to read data from foreign tables |
| Previous Message | Tom Lane | 2025-12-01 15:54:09 | Re: BUG #19338: [PG15] Unstable SQL result in test regress/tablespace |