Re: SQL-standard function body - Mailing list pgsql-hackers
From | Andres Freund |
---|---|
Subject | Re: SQL-standard function body |
Date | |
Msg-id | 20210408063320.eciql3ay52ge5flz@alap3.anarazel.de Whole thread Raw |
In response to | Re: SQL-standard function body (Tom Lane <tgl@sss.pgh.pa.us>) |
Responses |
Re: SQL-standard function body
|
List | pgsql-hackers |
Hi, On 2021-04-08 02:05:25 -0400, Tom Lane wrote: > So far the buildfarm seems to be turning green after b3ee4c503 ... > so I wonder what extra condition is needed to cause the failure > Andres is seeing. Nothing special, really. Surprised the BF doesn't see it: andres@awork3:~/build/postgres/dev-assert/vpath$ cat /tmp/test.conf force_parallel_mode=regress andres@awork3:~/build/postgres/dev-assert/vpath$ make -j48 -s && EXTRA_REGRESS_OPTS='--temp-config /tmp/test.conf' make -s-C contrib/pg_stat_statements/ check All of PostgreSQL successfully made. Ready to install. ... The differences that caused some tests to fail can be viewed in the file "/home/andres/build/postgres/dev-assert/vpath/contrib/pg_stat_statements/regression.diffs". A copy of the test summarythat you see above is saved in the file "/home/andres/build/postgres/dev-assert/vpath/contrib/pg_stat_statements/regression.out". ... andres@awork3:~/build/postgres/dev-assert/vpath$ head -n 30 /home/andres/build/postgres/dev-assert/vpath/contrib/pg_stat_statements/regression.diffs diff -du10 /home/andres/src/postgresql/contrib/pg_stat_statements/expected/pg_stat_statements.out /home/andres/build/postgres/dev-assert/vpath/contrib/pg_stat_statements/results/pg_stat_statements.out --- /home/andres/src/postgresql/contrib/pg_stat_statements/expected/pg_stat_statements.out 2021-04-06 09:08:42.688697932-0700 +++ /home/andres/build/postgres/dev-assert/vpath/contrib/pg_stat_statements/results/pg_stat_statements.out 2021-04-0723:30:26.876071024 -0700 @@ -118,37 +118,38 @@ ?column? | ?column? ----------+---------- 1 | test (1 row) DEALLOCATE pgss_test; SELECT query, calls, rows FROM pg_stat_statements ORDER BY query COLLATE "C"; query | calls | rows ------------------------------------------------------------------------------+-------+------ PREPARE pgss_test (int) AS SELECT $1, $2 LIMIT $3 | 1 | 1 - SELECT $1 +| 4 | 4 + PREPARE pgss_test (int) AS SELECT $1, 'test' LIMIT 1; | 1 | 1 + SELECT $1 +| 8 | 8 +| | AS "text" | | - SELECT $1 + $2 | 2 | 2 - SELECT $1 + $2 + $3 AS "add" | 3 | 3 - SELECT $1 AS "float" | 1 | 1 - SELECT $1 AS "int" | 2 | 2 + SELECT $1 + $2 | 4 | 4 + SELECT $1 + $2 + $3 AS "add" | 6 | 6 + SELECT $1 AS "float" | 2 | 2 + SELECT $1 AS "int" | 4 | 4 SELECT $1 AS i UNION SELECT $2 ORDER BY i | 1 | 2 - SELECT $1 || $2 | 1 | 1 - SELECT pg_stat_statements_reset() | 1 | 1 Too tired to figure out why the BF doesn't see this. Perhaps the extra settings aren't used because it's scripted as an install check? Greetings, Andres Freund
pgsql-hackers by date: