From 72924c391237f35861d33ce6533cf0a43c2956f7 Mon Sep 17 00:00:00 2001 From: James Coleman Date: Fri, 27 Mar 2020 11:20:36 -0400 Subject: [PATCH v42 07/12] remove test todo --- src/test/regress/expected/incremental_sort.out | 3 --- src/test/regress/sql/incremental_sort.sql | 3 --- 2 files changed, 6 deletions(-) diff --git a/src/test/regress/expected/incremental_sort.out b/src/test/regress/expected/incremental_sort.out index 689143456e..65604b3429 100644 --- a/src/test/regress/expected/incremental_sort.out +++ b/src/test/regress/expected/incremental_sort.out @@ -43,9 +43,6 @@ select * from (select * from tenk1 order by four) t order by four, ten; (6 rows) reset work_mem; --- TODO if an analyze happens here the plans might change; should we --- solve by inserting extra rows or by adding a GUC that would somehow --- forcing the time of plan we expect. create table t(a integer, b integer); -- A single large group tested around each mode transition point. insert into t(a, b) select 1, i from generate_series(1, 100) n(i); diff --git a/src/test/regress/sql/incremental_sort.sql b/src/test/regress/sql/incremental_sort.sql index e567a9a14d..040324be32 100644 --- a/src/test/regress/sql/incremental_sort.sql +++ b/src/test/regress/sql/incremental_sort.sql @@ -16,9 +16,6 @@ explain (costs off) select * from (select * from tenk1 order by four) t order by four, ten; reset work_mem; --- TODO if an analyze happens here the plans might change; should we --- solve by inserting extra rows or by adding a GUC that would somehow --- forcing the time of plan we expect. create table t(a integer, b integer); -- A single large group tested around each mode transition point. -- 2.17.1