Re: adding tab completions

Alvaro Herrera <alvherre@2ndquadrant.com>

From: Alvaro Herrera <alvherre@2ndquadrant.com>

To: Justin Pryzby <pryzby@telsasoft.com>

Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2018-05-29T14:12:27Z

Lists: pgsql-hackers

Is it just me that finds shocking the notion of vacuuming a foreign
table?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

Improve tab completion for ANALYZE, EXPLAIN, and VACUUM.
- 121213d9d852 12.0 landed
Minor fixes for psql tab completion.
- 12368f5e83e7 11.0 landed
- 7046d3024605 12.0 landed
Add parenthesized options syntax for ANALYZE.
- 854dd8cff523 11.0 cited
Don't allow VACUUM VERBOSE ANALYZE VERBOSE.
- 921059bd66c7 11.0 cited
Parameter toast_tuple_target controls TOAST for new rows
- c2513365a0a8 11.0 cited
Add hash partitioning.
- 1aba8e651ac3 11.0 cited
Allow multiple tables to be specified in one VACUUM or ANALYZE command.
- 11d8d72c27a6 11.0 cited
Don't uselessly rewrite, truncate, VACUUM, or ANALYZE partitioned tables.
- 3c3bb99330aa 10.0 cited
Remove deprecated COMMENT ON RULE syntax
- e8d016d81940 10.0 cited
Add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies.
- ede62e56fbe8 9.6.0 cited
Extend EXPLAIN to allow generic options to be specified.
- d4382c4ae7ea 9.0.0 cited