summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-01-18 16:33:18 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2017-01-18 16:33:57 -0500
commit6290f8e966ef3e2796522a3ea11b087a99f63413 (patch)
treecab76ece064736ac7cbd597a6b9c9a04b331e97a
parent75c155f65b046686242ece4bbfb688359f28feea (diff)
Reset the proper GUC in create_index test.
Thinko in commit a4523c5aa. It doesn't really affect anything at present, but it would be a problem if any tests added later in this file ought to get index-only-scan plans. Back-patch, like the previous commit, just to avoid surprises in case we add such a test and then back-patch it. Nikita Glukhov Discussion: https://postgr.es/m/8b70135d-ad38-bdd8-ac92-71e2b3c273cf@postgrespro.ru
-rw-r--r--src/test/regress/expected/create_index.out2
-rw-r--r--src/test/regress/sql/create_index.sql2
2 files changed, 2 insertions, 2 deletions
diff --git a/src/test/regress/expected/create_index.out b/src/test/regress/expected/create_index.out
index 2f05d51fff9..728cd1eabe7 100644
--- a/src/test/regress/expected/create_index.out
+++ b/src/test/regress/expected/create_index.out
@@ -2792,7 +2792,7 @@ ORDER BY thousand;
1 | 1001
(2 rows)
-RESET enable_indexscan;
+RESET enable_indexonlyscan;
--
-- Check elimination of constant-NULL subexpressions
--
diff --git a/src/test/regress/sql/create_index.sql b/src/test/regress/sql/create_index.sql
index 989fc97eee7..5008e981ab0 100644
--- a/src/test/regress/sql/create_index.sql
+++ b/src/test/regress/sql/create_index.sql
@@ -943,7 +943,7 @@ SELECT thousand, tenthous FROM tenk1
WHERE thousand < 2 AND tenthous IN (1001,3000)
ORDER BY thousand;
-RESET enable_indexscan;
+RESET enable_indexonlyscan;
--
-- Check elimination of constant-NULL subexpressions