From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Make postgres_fdw's query_cancel test less flaky. |
Date: | 2025-03-07 07:40:17 |
Message-ID: | Z8qi4VASbb9aT4MA@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Hi Tom,
On Fri, Aug 30, 2024 at 08:47:46PM +0000, Tom Lane wrote:
> Make postgres_fdw's query_cancel test less flaky.
>
> This test occasionally shows
>
> +WARNING: could not get result of cancel request due to timeout
>
> which appears to be because the cancel request is sometimes unluckily
> sent to the remote session between queries, and then it's ignored.
>
> Back-patch to v17 where this test was introduced.
Based on this recent report from the buildfarm, there is still
something happening here:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-03-07%2004%3A31%3A37
In details:
-- This would take very long if not canceled:
SELECT count(*) FROM ft1 a CROSS JOIN ft1 b CROSS JOIN ft1 c CROSS JOIN ft1 d;
ERROR: canceling statement due to statement timeout
+WARNING: could not send cancel request: cancel request timed out
COMMIT;
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2025-03-07 09:35:16 | pgsql: Allow casting between bytea and integer types. |
Previous Message | Jeff Davis | 2025-03-07 03:40:24 | pgsql: CREATE INDEX: don't update table stats if autovacuum=off. |