mirror of https://github.com/postgres/postgres
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
34 lines
1.7 KiB
34 lines
1.7 KiB
SELECT version() ~ 'cygwin' AS skip_test \gset
|
|
\if :skip_test
|
|
\quit
|
|
\endif
|
|
-- Let's test canceling a remote query. Use a table that does not have
|
|
-- remote_estimate enabled, else there will be multiple queries to the
|
|
-- remote and we might unluckily send the cancel in between two of them.
|
|
-- First let's confirm that the query is actually pushed down.
|
|
EXPLAIN (VERBOSE, COSTS OFF)
|
|
SELECT count(*) FROM ft1 a CROSS JOIN ft1 b CROSS JOIN ft1 c CROSS JOIN ft1 d;
|
|
QUERY PLAN
|
|
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
|
Foreign Scan
|
|
Output: (count(*))
|
|
Relations: Aggregate on ((((public.ft1 a) INNER JOIN (public.ft1 b)) INNER JOIN (public.ft1 c)) INNER JOIN (public.ft1 d))
|
|
Remote SQL: SELECT count(*) FROM ((("S 1"."T 1" r1 INNER JOIN "S 1"."T 1" r2 ON (TRUE)) INNER JOIN "S 1"."T 1" r4 ON (TRUE)) INNER JOIN "S 1"."T 1" r6 ON (TRUE))
|
|
(4 rows)
|
|
|
|
BEGIN;
|
|
-- Make sure that connection is open and set up.
|
|
SELECT count(*) FROM ft1 a;
|
|
count
|
|
-------
|
|
822
|
|
(1 row)
|
|
|
|
-- On most machines, 10ms will be enough to be sure that we've sent the slow
|
|
-- query. We may sometimes exercise the race condition where we send cancel
|
|
-- before the remote side starts the query, but that's fine too.
|
|
SET LOCAL statement_timeout = '10ms';
|
|
-- 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
|
|
COMMIT;
|
|
|