Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[YSQL] Partially enable ANALYZE, VACUUM #2217

Closed
jaki opened this issue Sep 4, 2019 · 1 comment
Closed

[YSQL] Partially enable ANALYZE, VACUUM #2217

jaki opened this issue Sep 4, 2019 · 1 comment
Assignees
@jaki
Labels
area/ysql Yugabyte SQL (YSQL)

Comments

@jaki
Copy link
Contributor

jaki commented Sep 4, 2019

Enable ANALYZE and VACUUM in the grammar as beta features. However, make them no-ops in certain cases. For ANALYZE, Yugabyte relations (e.g. non-temporary tables) should do nothing. For VACUUM, nothing should be done in either case.

This is a small step for issue #1420.
@jaki jaki added the area/ysql Yugabyte SQL (YSQL) label Sep 4, 2019
@jaki jaki self-assigned this Sep 4, 2019
jaki pushed a commit that referenced this issue Sep 6, 2019
[YSQL][#2217] Enable ANALYZE, VACUUM in grammar
c030c7a 
Summary:
Enable the `ANALYZE` and `VACUUM` statements as beta features in
`gram.y`.  Disable `ANALYZE` for Yugabyte relations, and disable
`VACUUM` when Yugabyte is enabled.

Test Plan:
* Jenkins
* `TestPgMisc` java test
* `yb_pg_plpgsql` regress test of `TestPgRegressBetaFeatures` java test

Reviewers: neha, mihnea

Reviewed By: mihnea

Subscribers: yql

Differential Revision: https://phabricator.dev.yugabyte.com/D7160
@jaki
Copy link
Contributor Author

jaki commented Sep 11, 2019

Closed by commit c030c7a.

@jaki jaki closed this as completed Sep 11, 2019
@m-iancu m-iancu mentioned this issue Feb 26, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jaki jaki

Labels
area/ysql Yugabyte SQL (YSQL)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jaki