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

Make optional the analyze part in CDB_EstimateRowCount #301

Open
ethervoid opened this issue May 24, 2017 · 3 comments
Open

Make optional the analyze part in CDB_EstimateRowCount #301

ethervoid opened this issue May 24, 2017 · 3 comments

Comments

@ethervoid
Copy link
Contributor

The CDB_EstimateRowCount function executes an ANALYZE in the affected tables of the query when that tables don't have stats. But this operation could come at a great cost if, for example, the table is big so we should add an optional parameter to skip the analyze part where performance is more important and we can deal with tables without stats.

This issue arises because in the tiler we're using this function to gather stats from the layer queries and execute an ANALYZE could penalize the performance

@rafatower
Copy link
Contributor

is this required to go out with vector/raster?

@rafatower rafatower removed their assignment May 24, 2017
@ethervoid
Copy link
Contributor Author

Due to a conversation with @javisantana I think is a nice to have more than a must

@javisantana
Copy link
Contributor

I don't think this is critical but there are a few things why we should change this:

  • writing in a function that is created to get data seems not fine.
  • calling this function with different users could give different results
  • depending on that statistics target it cold take a while and this function was created to be fast (that's why we are estimating and not counting)

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

No branches or pull requests

3 participants