-
Notifications
You must be signed in to change notification settings - Fork 54
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
Comments
On Sat, Oct 19, 2019 at 7:58 PM Chris Cleveland ***@***.***> wrote:
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.
You are welcome, Chris !
GIN has a better scalability than GiST for full text search.
… —
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#69?email_source=notifications&email_token=ABQURYR75BH3NKJH526HTSDQPNDEJA5CNFSM4JCQZWBKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HS6FJCA>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQURYR3UX2LPUEL3VNYRD3QPNDEJANCNFSM4JCQZWBA>
.
--
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
|
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? |
On Mon, Oct 21, 2019 at 5:13 PM Chris Cleveland ***@***.***> wrote:
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?
src/backend/access/gin/README
—
… You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#69?email_source=notifications&email_token=ABQURYQSBTS5ZUI2YMICMKLQPXBJVA5CNFSM4JCQZWBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB2VSWQ#issuecomment-544561498>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQURYW5K42IQE4KQ6HQHF3QPXBJVANCNFSM4JCQZWBA>
.
--
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
|
Thank you, perfect. |
At the very bottom of the README, there is this comment: Distant future:
Can you explain a bit more? |
Фд
On Mon, Oct 21, 2019 at 9:44 PM Chris Cleveland ***@***.***> wrote:
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?
Read https://www.pgcon.org/2014/schedule/events/696.en.html
Also, I have some talks about indexing
http://www.sai.msu.su/~megera/postgres/talks/
You can use google translate and read 6 papers about indexes in postgres
https://habr.com/ru/company/postgrespro/blog/337502/
…
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
--
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: