Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[PGPRO-12159] Added functions for exploring the pages of the rum index.#150

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

Open
arseny114 wants to merge7 commits intopostgrespro:master
base:master
Choose a base branch
Loading
fromarseny114:PGPRO-12159

Conversation

arseny114
Copy link
Contributor

Six functions have been developed to extract information from the pages of the RUM index:

  1. rum_metapage_info() -- is used to examine the information that is placed on the meta page (flags: {meta}).
  2. rum_page_opaque_info() -- is used to examine information that is placed in the opaque area of the index page (any index page).
  3. rum_leaf_data_page_items() -- is used to examine the information that is placed on the leaf pages of the posting tree (flags: {leaf, data}).
  4. rum_internal_data_page_items() -- it is intended for viewing information that is located on the internal pages of the posting tree (flags {data}).
  5. rum_leaf_entry_page_items() -- it is intended for viewing information that is located on the leaf pages of the entry tree (flags {leaf}).
  6. rum_internal_entry_page_items() -- it is intended for viewing information that is located on the internal pages of the entry tree (flags {}).

To extract information, all these functions need to pass the index name and the page number.

Tags: rum

@arseny114arseny114 changed the titleAdded functions for exploring the pages of the rum index.[PGPRO-12159] Added functions for exploring the pages of the rum index.May 13, 2025
@arseny114arseny114force-pushed thePGPRO-12159 branch 2 times, most recently from1557119 tod13ae48CompareMay 14, 2025 16:01
arseny114and others added7 commitsMay 15, 2025 12:00
This commit adds three functions for low-level explorationof the index's rum pages:1) rum_metapage_info() -- is used to examine the informationposted on the meta page (flags: {meta}).2) rum_page_opaque_info() -- is used to examine informationthat is placed in the opaque area of the index page (anyindex page).3) rum_leaf_data_page_items() -- is used to examine theinformation that is placed on the leaf pages of theposting tree (flags: {leaf, data}).To extract information, all these functions need to passthe index name and the page number.Tags: rum
1) rum_internal_data_page_items() - it is intended for viewing information   that is located on the internal pages of the posting tree (flags {data}).2) rum_leaf_entry_page_items() - it is intended for viewing information   that is located on the leaf pages of the entry tree (flags {leaf}).3) rum_internal_entry_page_items() - it is intended for viewing information   that is located on the internal pages of the entry tree (flags {}).To extract information, all these functions need to pass the index nameand the page number.Tags: rum
If you create an index with the operator class rum_tsvector_ops,the positions of the lexemes will be saved as additional information.The positions are stored in compressed form in bytea.There is a problem that is related to the fact that in the posting tree,additional information for the senior keys is stored in a different way,which is why it has not yet been possible to output it. For all othercases, the output of additional information works correctly.Tags: rum
If the index is created with the appropriate class of operators,then in addition to the positions of the lexemes, weights (A, B, C, D)are also stored in the additional information. Their output has been added.In addition, Asserts have been added to the find_add_info_atr_num() andfind_add_info_oid() functions, which check that there is only one (or zero)type of additional information in the index.Tags: rum
The crashes were due to the fact that the construct_array_builtin()function is not defined on versions below 16.Tags: rum
The crashes were due to the fact that the errdetail_relkind_not_supported()function is not defined on versions below 15.Tags: rum
The crashes were due to the fact that theMONEYOID is not defined on versions below 14.Tags: rum
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

1 participant
@arseny114

[8]ページ先頭

©2009-2025 Movatter.jp