pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Rowley <dgrowleyml@gmail.com>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix test case from b0c5b215d.
Date: Mon, 29 Apr 2024 22:14:28 -0400
Message-ID: <1544493.1714443268@sss.pgh.pa.us> (raw)
In-Reply-To: <1539986.1714441226@sss.pgh.pa.us>
References: <E1s1bHM-000hcK-87@gemulon.postgresql.org>
	<CAApHDvo8pMk5WWFAqwGzuQ-Xh+957W61io_OsCP0oUzqCCODTg@mail.gmail.com>
	<1539986.1714441226@sss.pgh.pa.us>

I wrote:
> I committed that suggestion, but I'm not sure it's enough to fix it,
> because if I do
> 	LANG=cs_CZ.utf8 make check
> then I still get variant output order.  I tried about six different
> spellings of the query without improving matters, so I'm totally
> baffled.  Have we managed to break COLLATE "C"?  (With one eye on
> Jeff Davis' recent stuff, I could believe that, except I'd have
> expected it to show up in other regression tests already.)

Yeah, the affected buildfarm members seem still not happy.

In simple testing such as
	select * from foo order by f1 collate "C";
the behavior seems as expected.  I also confirmed that I see the test
misbehavior locally with or without ICU.  So I kind of think that this
is not a failure in the sorting code per se.  My current idea is that
in a more complicated query such as the new test_pg_dump query, we are
somehow losing the COLLATE "C" specification --- it's there in the
Sort node according to EXPLAIN VERBOSE, but it sure doesn't seem to be
having any effect.

I'm too tired to look any closer tonight, though.

			regards, tom lane





view thread (9+ messages)  latest in thread

Message-ID: <1544493.1714443268@sss.pgh.pa.us>
Permalink:  ../1544493.1714443268@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1544493.1714443268@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, dgrowleyml@gmail.com, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Fix test case from b0c5b215d.
  In-Reply-To: <1544493.1714443268@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox