- Notifications
You must be signed in to change notification settings - Fork15
Configurable smoc_gin_ops index resolution#86
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
This is a useful new feature for me, so +1 on that account. I've lightly reviewed the code and have found no reason to complain (disclaimer: I'm no expert for PG indexing).
d01bd7d toc72377aCompareUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Back when smoc GIN indexes were implemented, indexes did not supportopclass options yet; that was added only later in PG 13.Add an "order" parameter on the smoc_gin_ops opclass to allow pickingthe smoc index granularity between level 0 and 12. (Larger levels do notfit into the internal int32 datatype anymore.)Example:`create index on sky using gin (coverage smoc_gin_ops (order = 8))`
Back when smoc GIN indexes were implemented, indexes did not support opclass options yet; that was added only later in PG 13.
Add an "order" parameter on the smoc_gin_ops opclass to allow picking the smoc index granularity between level 0 and 12. (Larger levels do not fit into the internal int32 datatype anymore.)
Example:
create index on sky using gin (coverage smoc_gin_ops (order = 8))