diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-01-15 12:07:10 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-01-15 12:07:10 -0500 |
| commit | 1c53c4dec3985512f7f2f53c9d76a5295cd0a2dd (patch) | |
| tree | d73a6f1954718d48d622162c98bfa6ca5ddc2422 /src/bin/psql/tab-complete.c | |
| parent | 0944ec54de389b4b8a471ca1f40f1b9d81de1f30 (diff) | |
Finish reverting "recheck_on_update" patch.
This reverts commit c203d6cf8 and some follow-on fixes, completing the
task begun in commit 5d28c9bd7. If that feature is ever resurrected,
the code will look quite a bit different from this, so it seems best
to start from a clean slate.
The v11 branch is not touched; in that branch, the recheck_on_update
storage option remains present, but nonfunctional and undocumented.
Discussion: https://postgr.es/m/20190114223409.3tcvejfhlvbucrv5@alap3.anarazel.de
Diffstat (limited to 'src/bin/psql/tab-complete.c')
| -rw-r--r-- | src/bin/psql/tab-complete.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/bin/psql/tab-complete.c b/src/bin/psql/tab-complete.c index bca788c7a33..292b1f483a9 100644 --- a/src/bin/psql/tab-complete.c +++ b/src/bin/psql/tab-complete.c @@ -1623,14 +1623,14 @@ psql_completion(const char *text, int start, int end) COMPLETE_WITH("("); /* ALTER INDEX <foo> SET|RESET ( */ else if (Matches("ALTER", "INDEX", MatchAny, "RESET", "(")) - COMPLETE_WITH("fillfactor", "recheck_on_update", + COMPLETE_WITH("fillfactor", "vacuum_cleanup_index_scale_factor", /* BTREE */ "fastupdate", "gin_pending_list_limit", /* GIN */ "buffering", /* GiST */ "pages_per_range", "autosummarize" /* BRIN */ ); else if (Matches("ALTER", "INDEX", MatchAny, "SET", "(")) - COMPLETE_WITH("fillfactor =", "recheck_on_update =", + COMPLETE_WITH("fillfactor =", "vacuum_cleanup_index_scale_factor =", /* BTREE */ "fastupdate =", "gin_pending_list_limit =", /* GIN */ "buffering =", /* GiST */ |