From e75d99818dd3940be997520e64db8c9e3b207e39 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 21 May 2024 07:05:26 +0200 Subject: Merging upstream version 15.7. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/how-parallel-query-works.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/how-parallel-query-works.html') diff --git a/doc/src/sgml/html/how-parallel-query-works.html b/doc/src/sgml/html/how-parallel-query-works.html index 740aa11..18cab3a 100644 --- a/doc/src/sgml/html/how-parallel-query-works.html +++ b/doc/src/sgml/html/how-parallel-query-works.html @@ -1,5 +1,5 @@ -15.1. How Parallel Query Works

15.1. How Parallel Query Works

+15.1. How Parallel Query Works

15.1. How Parallel Query Works

When the optimizer determines that parallel query is the fastest execution strategy for a particular query, it will create a query plan that includes a Gather or Gather Merge @@ -68,4 +68,4 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%'; order-preserving merge. In contrast, Gather reads tuples from the workers in whatever order is convenient, destroying any sort order that may have existed. -

\ No newline at end of file +

\ No newline at end of file -- cgit v1.2.3