From: Tom Lane <tgl@sss.pgh.pa.us>
To: d.kovalenko@postgrespro.ru
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19338: [PG15] Unstable SQL result in test regress/tablespace
In-reply-to: <19338-3dd4f9982d9b55a9@postgresql.org>
References: <19338-3dd4f9982d9b55a9@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 01 Dec 2025 11:31:19 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <192740.1764604449.1@sss.pgh.pa.us>
Date: Mon, 01 Dec 2025 10:54:09 -0500
Message-ID: <192741.1764604449@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/192741.1764604449%40sss.pgh.pa.us>
Precedence: bulk

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