Message-ID: <507b05d3-ecc7-4840-afbd-c5098585f051@postgrespro.ru>
Date: Mon, 1 Dec 2025 19:52:47 +0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: BUG #19338: [PG15] Unstable SQL result in test regress/tablespace
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
References: <19338-3dd4f9982d9b55a9@postgresql.org>
 <192741.1764604449@sss.pgh.pa.us>
Content-Language: ru, en-US
From: Dmitry Kovalenko <d.kovalenko@postgrespro.ru>
In-Reply-To: <192741.1764604449@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/507b05d3-ecc7-4840-afbd-c5098585f051%40postgrespro.ru>
Precedence: bulk

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@postgresql.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