Re: pg_stat_statements: more test coverage
От | Julien Rouhaud |
---|---|
Тема | Re: pg_stat_statements: more test coverage |
Дата | |
Msg-id | CAOBaU_ZJC=Wxtocz3KAiOWKFSqvuNkvb_A86mZccqd3seAODiQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_stat_statements: more test coverage (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: pg_stat_statements: more test coverage
|
Список | pgsql-hackers |
On Sun, Dec 31, 2023 at 2:28 PM Michael Paquier <michael@paquier.xyz> wrote: > > On Sat, Dec 30, 2023 at 08:39:47PM +0100, Peter Eisentraut wrote: > > Ok, I have committed these two patches. > > Please note that the buildfarm has turned red, as in: > https://buildfarm.postgresql.org/cgi-bin/show_stagxe_log.pl?nm=pipit&dt=2023-12-31%2001%3A12%3A22&stg=misc-check > > pg_stat_statements's regression.diffs holds more details: > SELECT query FROM pg_stat_statements WHERE query LIKE '%t001%' OR query LIKE '%t098%' ORDER BY query; > query > -------------------- > - select * from t001 > select * from t098 > -(2 rows) > +(1 row) That's surprising. I wanted to see if there was any specific configuration but I get a 403. I'm wondering if this is only due to other tests being run concurrently evicting an entry earlier than planned.
В списке pgsql-hackers по дате отправления: