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.

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

Update Cost Based Optimizer docs section "Preferring the nearest index" to describe new reality #10391

Closed
rmloveland opened this issue Apr 21, 2021 · 4 comments
Assignees
Milestone

Comments

@rmloveland
Copy link
Contributor

We still have this huge section in the optimizer docs on Preferring the nearest index, which needs to be updated since it refers to Ye Olde "duplicate indexes" and has a bunch of explicit zone configs n stuff.

Options for dealing with this include:

  • Replace it with a section called "multi-region index selection" or similar?
  • Remove it altogether? Since maybe users get this all "for free" now from the optimizer when they add indexes to tables in multi-region DBs? Is it enough to rely on the index change descriptions in Add docs on indexing of REGIONAL BY ROW tables #10280?
  • ???
  • profit, etc.
@rmloveland rmloveland self-assigned this Apr 21, 2021
@rmloveland rmloveland added this to the 21.1 milestone Apr 21, 2021
@rmloveland
Copy link
Contributor Author

Hey @ianjevans since (I think?) you are the optimizer docs person (?) - FYI I am planning some updates to this section of the page re: multi-region things

@ianjevans
Copy link
Contributor

I've got some updates to this page forthcoming in #10324, but I don't think they affect that section. It should be merged in the next day or two.

@rmloveland
Copy link
Contributor Author

rmloveland commented Apr 22, 2021 via email

@rmloveland
Copy link
Contributor Author

Went with the 2nd option - remove altogether (in #10465), since you now get this behavior automagically from multi-region databases.

Closing ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants