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

Newly created database system indices has 0 selectivity. [CORE3728] #4074

Open
firebird-automations opened this issue Jan 13, 2012 · 6 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Attila Molnár (e_pluribus_unum)

Is duplicated by CORE3742

Hi!

Newly created database system indices has 0 selectivity. Creation should include statistic refresh at the end.

@firebird-automations
Copy link
Collaborator Author

Modified by: Attila Molnár (e_pluribus_unum)

description: Hi!

Newly created database system table indicies has 0 selectivity. Creation should include statistic refresh at the end.

=>

Hi!

Newly created database system indices has 0 selectivity. Creation should include statistic refresh at the end.

summary: Newly created database system table index selectivity 0 => Newly created database system indices has 0 selectivity.

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

Do you mean a newly created, but empty database?

If so, since the database is empty; why does it matter?

@firebird-automations
Copy link
Collaborator Author

Commented by: Attila Molnár (e_pluribus_unum)

The database is not empty it contaions system tables with data, and system indices, etc...
DLL commands uses system indices, but with 0 selectivity it has no use until you set index statistics directly for system indices.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue is duplicated by CORE3742 [ CORE3742 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @ibaseru

indices created on empty tables have selectivity = 0.
when tables are filled with data, these indices will still have selectivity = 0, because selectivity is being recomputed only when SET STATISTICS command applied, or when index re-activated on non-empty table (or, when restore from backup is made, because indices are created after data already pumped from backup).

I.e., there is no atomatic statistics recomputation.

@EPluribusUnum
Copy link

This is still an issue (Tested with FB30 and FB40)

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

2 participants