From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, tharar(at)amazon(dot)com |
Subject: | Re: wrong query results on bf leafhopper |
Date: | 2025-05-20 04:07:23 |
Message-ID: | 611611.1747714043@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> Note that the actual row count is 1000 still, so that pretty much
> discounts corruption with the stored unique1 values. Unfortunately,
> that doesn't reduce the number of possible other reasons by very much.
Failures like this one [1]:
@@ -340,9 +340,13 @@
create function myinthash(myint) returns integer strict immutable language
internal as 'hashint4';
NOTICE: argument type myint is only a shell
+ERROR: ROWS is not applicable when function does not return a set
are hard to explain as anything besides "that machine is quite
broken". Whether it's flaky hardware, broken compiler, or what is
undeterminable from here, but I don't believe it's our bug. So I'm
unexcited about putting effort into it.
regards, tom lane
[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-05-19%2007%3A07%3A04
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2025-05-20 04:09:44 | Re: Document default values for pgoutput options + fix missing initialization for "origin" |
Previous Message | Michael Paquier | 2025-05-20 03:59:13 | Re: Regression in statement locations |