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

Why GIN and not GiST? #69

Open
ccleve opened this issue Oct 19, 2019 · 6 comments
Open

Why GIN and not GiST? #69

ccleve opened this issue Oct 19, 2019 · 6 comments

Comments

@ccleve
Copy link

ccleve commented Oct 19, 2019

I'm just starting to get into Postgres development. I'm trying to understand index structures and how to extend them. I noticed that you folks are also the ones that maintain the Postgres GiST code. Why did you choose to base RUM on GIN instead of GiST?

Sorry for the newbie question -- I'm not familiar with the Postgres code base yet. I did find some (short) references on creating new GiST indexes, but nothing on GIN, and I'm finding the code hard to follow.

@obartunov
Copy link

obartunov commented Oct 21, 2019 via email

@ccleve
Copy link
Author

ccleve commented Oct 21, 2019

Can you give a few more details? I haven't been able to find good documentation on the underlying file formats of the different index types. Do you know of any docs that explain how GIN indexes are formatted internally, and how to modify them?

@obartunov
Copy link

obartunov commented Oct 21, 2019 via email

@ccleve
Copy link
Author

ccleve commented Oct 21, 2019

Thank you, perfect.

@ccleve ccleve closed this as completed Oct 21, 2019
@ccleve
Copy link
Author

ccleve commented Oct 21, 2019

At the very bottom of the README, there is this comment:

Distant future:

  • Replace B-tree of entries to something like GiST

Can you explain a bit more?

@ccleve ccleve reopened this Oct 21, 2019
@obartunov
Copy link

obartunov commented Oct 22, 2019 via email

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